Access Provider Template
Overview
The Access Provider template accelerates the speed of development for an app that uses the OIDC Provider. Currently it shows how you can build an Access Provider app that
- uses the OIDC Provider to issue Access Tokens to clients using the Client Credential grant
- uses the OIDC SSO module so local admins can login to the Access Provider via SSO, rather than using local credentials.
The Access Provider template helps you set up and integrate OIDC Provider and OIDC SSO modules. It includes all the necessary dependencies, so you do not need to install them separately. The template also comes with predefined administration role, making it easier to manage the access rights. Additionally, it provides navigations and configurations for seamless usage of the OIDC Provider and OIDC SSO modules.
If you would like to use the Access Provider Template, please send an email to jaap.francke@mendix.com
Documentation
Features
The Access Provider template allows you to focus on utilizing the below features without dealing with complex setup procedures.
1. Comprehensive setup of OIDC Provider module.
2. Set up of OIDC SSO module for login of Administrators, eliminating the need for local MxAdmin credentials
2. Inclusion of all necessary dependencies for the modules
3. Pre-configured user roles and navigation settings
Using Access Provider Template:
1. Select the Access Provider template when creating the application.
2. Utilize the deploy time configuration feature of the OIDC SSO module. For more information, see the Automated Deploy-time SSO Configuration section of the OIDC SSO. This feature helps you create the client configuration during application deployment, without the need for local credentials to login.
Note: Ensure that the user role is set to Administrator to access Navigation pages which has Administrator user roles.
By default, any user with SSO access to the Provider app can be considered an Admin. To avoid this, you can either:
- Restrict access through IdP: Limit app access through their Identity Provider to specific users.
- Modify app/template: Adjust the app/template to check for specific scopes, groups, or claims as per the OIDC SSO module.
3. Make sure to set the Encryption key to 32 characters before running the application.
4. Once you create the configuration, log into the application using SSO.