Difference between revisions of "OAuth 2.0"
| Line 2: | Line 2: | ||
[[File:OAuth2_logo.png|200px]] | [[File:OAuth2_logo.png|200px]] | ||
| + | |||
| + | == Features == | ||
| + | *'''Secure:''' | ||
| + | ::Users are not required to share their passwords with 3rd party applications, increasing account security. | ||
| + | *'''Standard:''' | ||
| + | ::A wealth of client libraries and example code are compatible with SoFurry's OAuth implementation. | ||
| + | *'''Easy:''' | ||
| + | ::Using OAuth is easy for both users and developers. All a user has to do to grant access to a certain application is to klick on the "Authorize" button on SoFurry when asked. | ||
Revision as of 21:13, 5 March 2016
SoFurry uses OAuth 2.0 to provide authorized access to its API.
Error creating thumbnail: File missing
Features
- Secure:
- Users are not required to share their passwords with 3rd party applications, increasing account security.
- Standard:
- A wealth of client libraries and example code are compatible with SoFurry's OAuth implementation.
- Easy:
- Using OAuth is easy for both users and developers. All a user has to do to grant access to a certain application is to klick on the "Authorize" button on SoFurry when asked.
