Have you implemented OpenMRS? Please participate in the Implementation Site Survey. If you already have, thank you!
When modules are installed in OpenMRS, the filters are loaded in the order of installation. Therefore make sure that there are so such conflicts when installing the OAuth2 module and OAuth2 module's filters (spring security filter chain) are loaded before filters of protected modules.
Upon successful installation the following tables will be added to the database :
|1||oauth2_client||stores basic information about registered clients|
|2||oauth2_client_authorities||stores the granted authorities for registered clients (ROLE_CLIENT for now)|
|3||oauth2_client_grant_types||stores authorization grant types for registered clients|
|4||oauth2_client_redirect_uri||stores redirect_uri's for registered clients|
|5||oauth2_client_resource_ids||stores the permitted resource id's for registered clients|
|6||oauth2_client_scopes||stores the scope for registered clients|
|7||oauth_access_token||stores access_tokens for each client. will be deprecated|
|8||oauth_client_token||stores access tokens|
|9||oauth_code||maintains authorization code|
|10||oauth_refresh_token||maintains refresh tokens|
Client Developers are those users of an OpenMRS installation that develop OAuth2 clients i.e applications that use OpenMRS's web services protected by the OAuth2 module. At present, all users are allowed to register OAuth2 clients (via the REST controller). This will be changing soon. Only users with proper roles and permissions (client_developer) will be allowed to register
The admins of OpenMRS instance will be see a list of all registered clients.
To manage clients using REST Controller see this