You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+21-5
Original file line number
Diff line number
Diff line change
@@ -4,21 +4,26 @@ Authorize users with your application in a driver-base fashion meaning one imple
4
4
5
5
Note that this Spark ONLY provides the authorization mechanism. There's an example controller below, however in a later version there will be a full controller.
6
6
7
-
## Currently Supported
7
+
## Examples
8
+
9
+
OAuth 2 is split into two sections, clients and providers. A client is an application - perhaps a basic Twitter feed aggregator - which
10
+
authenticates with an OAuth 2 provider, which in this example would be Twitter itself. You can interact with any provider which is supported in the list below:
8
11
9
12
- Facebook
10
13
- Foursquare
11
14
- GitHub
12
15
- Google
16
+
- PayPal
13
17
- Instagram
18
+
- Soundcloud
14
19
- Windows Live
15
20
- YouTube
16
21
17
-
## TODO
18
22
19
-
This is a developing library and currently only supports a small number of OAuth2 providers - more refactoring of code is to follow with a full implementation of an authentication class to store users details.
23
+
## TODO
20
24
21
-
Requests should be done through a more stable system, there however isn't a request class in CodeIgniter.
25
+
- Requests should be done through a more stable system, there however isn't a Request class in CodeIgniter.
26
+
- Add unit tests and get on Travis
22
27
23
28
## Usage Example
24
29
@@ -75,4 +80,15 @@ class Auth extends CI_Controller
75
80
}
76
81
```
77
82
78
-
If all goes well you should see a dump of user data and have `$token` available. If all does not go well you'll likely have a bunch of errors on your screen.
83
+
If all goes well you should see a dump of user data and have `$token` available. If all does not go well you'll likely have a bunch of errors on your screen.
84
+
85
+
Contribute
86
+
----------
87
+
88
+
1. Check for open issues or open a new issue for a feature request or a bug
89
+
2. Fork [the repository][] on Github to start making your changes to the
90
+
`develop` branch (or branch off of it)
91
+
3. Write a test which shows that the bug was fixed or that the feature works as expected
92
+
4. Send a pull request and bug me until I merge it
0 commit comments