OIDC
This documentation describes the process of integrating an OIDC application with Port, along with some examples for specific identity providers. In order to integrate Port with an OIDC SSO application, you will need to do the following:
- Create a new OIDC application in your identity provider and provide an app integration name, like
Port
. - Configure the application with the following details:
- Redirect URI:
https://auth.getport.io/login/callback
- Login URI:
https://auth.getport.io/authorize?response_type=token&client_id=96IeqL36Q0UIBxIfV1oqOkDWU6UslfDj&connection={CONNECTION_NAME}&redirect_uri=https%3A%2F%2Fapp.getport.io
noteWe will provide your
{CONNECTION_NAME}
(Contact us on Slack/Intercom).
- Redirect URI:
- Expose the application to your organization by either granting access to everyone or restricting it to specific roles.
- Share information about your SSO application:
- Provide Port with the following details:
Client ID
: The client identifier for your OIDC application.Client Secret
: The client secret for your OIDC application.
- Provide Port with the following details:
- Add a custom property
email_verified
and configure the OpenID Claims in your identity provider to ensure that Port receives the valuetrue
for this attribute as part of the connection process. This step may be required specifically for certain identity providers such as OneLogin. - Configure the Groups claim in the OpenID Connect Token settings to enable automatic groups or roles support in Port.
noteThis step is OPTIONAL and is required only if you wish to pull all of your groups or roles into Port inherently.
📄️ Microsoft Entra ID (AzureAD)
Integrate AzureAD with Port
📄️ Okta (OIDC)
Integrate Okta with Port
📄️ Onelogin
Integrate Onelogin with Port