Skip to content
This repository has been archived by the owner on Feb 20, 2019. It is now read-only.

Commit

Permalink
Document OAuth2 limitations and requirements
Browse files Browse the repository at this point in the history
Relates to #3464.
  • Loading branch information
settermjd committed Jun 1, 2018
1 parent 89d1863 commit f9fbb78
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions admin_manual/configuration/server/security/oauth2.rst
Original file line number Diff line number Diff line change
Expand Up @@ -139,7 +139,7 @@ For further information about client registration, please refer to `the official
Installation
------------

To install the application, place the content of the OAuth2 app inside your installation's ``app`` directory.
To install the application, place the content of the OAuth2 app inside your installation's ``app`` directory, or use the Market application.

Requirements
------------
Expand All @@ -152,11 +152,13 @@ Basic Configuration
Restricting Usage
-----------------

- Enterprise installations can limit the access of authorized clients, preventing unwanted clients from connecting.

Limitations
-----------

Since the app handles no user passwords, only master key encryption works (similar to `the Shibboleth app`_).
- Since the app handles no user passwords, only master key encryption works (similar to `the Shibboleth app`_).
- Clients cannot migrate accounts from Basic Authorization to OAuth2, if they are currently using the `~user_ldap~` backend.

Connecting Clients via OAuth2
-----------------------------
Expand Down

0 comments on commit f9fbb78

Please sign in to comment.