Clients and scopes
In the PERCEIVE Project, OAuth 2.0 is utilized to manage authentication and authorization, defining specific clients and scopes to control access to various resources. This article presents an overview of the clients and scopes within the project, outlining the access permissions and roles associated with each. The following tables summarize the available clients and their permitted scopes, as well as the scopes and their corresponding resources.
Clients Overview
The project defines two clients, each with specific permissions and roles. The table below details each client's ID, secret, consent type, display name, redirect URIs, post-logout redirect URIs, and permissions.
Display Name | Client ID | Client Secret | Consent Type | Redirect URIs | Post Logout Redirect URIs | Scopes |
|---|---|---|---|---|---|---|
Postman client application | postman-client | 901564A5-E7FE-42CB-B10D-61EF6A8F3654 | Explicit | http://localhost:5259/swagger/oauth2-redirect.html https://oauth.pstmn.io/v1/callback | http://localhost:5259/resources | identity_management, data_management, metadata_management |
Perceive Portal | perceive-portal | 3DCD29DB-FAFD-47D8-B8DA-56264FCF5AAD | Explicit | http://localhost:5259/swagger/oauth2-redirect.html https://oauth.pstmn.io/v1/callback | http://localhost:5259/resources | identity_management, data_management, metadata_management |
Scopes and Resources
Scopes are used to specify the access rights that applications can request. The table below lists the scopes available within the PERCEIVE Project, their display names, and the resources they are associated with.
Scope Name | Display Name | Resources |
|---|---|---|
identity_management | Account Management | identity_service_api |
data_management | Data Management | data_service_api, orchestrator_api |
metadata_management | Metadata Management | metadata_service_api, orchestrator_api |