Before You Begin
To complete this configuration, the individual will require the necessary permissions within Microsoft Entra and also be a Platform Admin within the Airia platform.Registering the Airia Application in Identity Provider
In order to connect to Airia via SSO, please first register the Airia application with your identity provider to enable SSO.Create an Application Registration
In your identity provider (Microsoft Entra), create a new app registration for the Airia platform.
Take note of the Application Registration (client) ID and Client Secret as this will not be visible later
Configure Redirect URI:
Under the app registration, navigate to the authentication configuration area.
Under the Platform Configurations heading, select ‘Add a Platform’.
Add a Web platform and enter the Redirect URI provided by Airia.
Save the changes by selecting ‘Configure’.
Obtain the Discovery Endpoint or OpenID Connect Metadata:
From the Airia app registration overview, head to the Endpoints tab.
Locate and copy the Discovery Endpoint to facilitate the endpoint mapping into the Airia platform.
Alternatively, to manually configure this, make note of the app URL metadata as this will be used to populate the Airia SSO configuration.
Configuring SSO in the Airia Platform
Now you have created the application within Entra, navigate to Airia to complete the SSO configuration within the Airia platform.Insert the Discovery Endpoint
- In the Airia SSO setup, the recommended path to take is to use the discovery endpoint method. If you have the Entra Discovery Endpoint, paste it into the Discovery endpoint field.
- If opting to use Custom Configuration, select that header and complete the fields with the information from the Entra OpenID Connect Metadata.
- Authorization URL
- Token URL
- Logout URL
- User Info URL
- Issuer
- Validation method
- PKCE
Enter Client ID and Secret:
Input the Application ID and the Client Secret that was created in previous step.Set Domains for Auto-Discovery:
Specify your organization’s domain(s).Set Default Role:
- For this, we suggest using the ‘End User’ role for an approach of least privileges.
- Platform Admin – complete access to the admin console.
- Admin – limited admin access to build agents but excludes access to functionality such as SSO, Account management and other Platform Admin privileges.
- End User – only accesses the agent catalogue to see deployed agents.
