Single sign-on (SSO) is a method of allowing a user to access multiple applications or platforms with a single sign-on.
Sidebar dropdown → Organisation → OIDC SSO Connection
Fill the fields under the OIDC SSO connection section
Setup the user roles automatically using OIDC
In the Organizations → OIDC settings, there are 2 options designed for this :
Option | Example of value | Description |
---|---|---|
OIDC Roles Map | { "editor": "Editor", "admin": "Admin", "viewer": "Reader", "restricted_viewer": "ReaderRestrict" } | This is a JSON object that contains the 4 feedier roles as keys (do not change them) and the SSO role in your IAM system.
|
OIDC Scopes |
| This is a comma separated list of information Feedier will ask for every SSO connection, the There must be no extra spaces in the field value. |
For any help, ask our team to help you set it up.
Example for Microsoft Active Directory
An App needs to be created from your Azure portal, you can call it Feedier.
Under API permissions, make sure to enable: Microsoft Graph
email
openid
User.Read
Authentication → Web → Redirect URIs: HTTPS://dashboard.feedier.com/auth/oidc/callback?organizationId={Organization ID in Feedier}
Then, in the organization settings:
URL name | Typical URL |
Discovery Endpoint | https://login.microsoftonline.com/{tenant_id}/v2.0/.well-known/openid-configuration |
Authorization Endpoint | https://login.microsoftonline.com/{tenant_id}/oauth2/v2.0/authorize |
Userinfo Endpoint | |
Token Endpoint | https://login.microsoftonline.com/{tenant_id}/oauth2/v2.0/token |
Base URL | https://login.microsoftonline.com/{tenant_id}/v2.0 |
The IDs and URLs with your custom ID can be found directly in the tool you want to use for SSO (e.g. Microsoft, Okta,...).
For further reading, here’s an example of adding an OpenID Connect-based single sign-on application:
Add Comment