Before you begin
You need a paid plan and permission to manage sign-in providers in the selected Organization. Account Owners and Administrators have this permission. A role assigned in a parent Organization also applies in its descendants. For an external provider, you also need permission to create or edit an OIDC web application. Raily shows provider-specific setup instructions. The redirect URI is generated after you attach the provider to an endpoint.Raily-hosted sign-in does not need external credentials. You manage its users and endpoint grants in Raily.
Choose a provider
Set up Raily-hosted sign-in
Raily creates a hosted sign-in when it creates a new Organization. If the selected Organization does not have one, the provider list shows Set up Raily sign-in.1
Open Sign-in providers
Go to Security → Access → Sign-in providers. If the selected Organization does not have a hosted provider, the setup banner appears above the provider list.

2
Set up Raily sign-in
Select Set up Raily sign-in and wait for Raily sign-in to appear as Verified and Active.

Configure an external OIDC provider
Keep Raily and your identity provider open while you work. The wizard shows how to create the OIDC application and where to find its client ID and client secret. You will add the endpoint-specific redirect URI after you attach the provider in Raily.1
Open the provider wizard
Go to Security → Access → Sign-in providers, then select Configure OAuth Provider.

2
Name the configuration
Open Provider and choose your identity provider. If yours is not listed, choose Custom, the last option, to connect any other OpenID Connect provider.
Enter an OAuth Client Name, then select Continue. The name only identifies this configuration in Raily.


3
Enter the provider credentials
Follow the setup instructions shown for your provider. They list the application type and the values to enter in your provider.
Enter the Issuer URL, Client ID, and Client Secret.For Google, you can upload the credentials JSON file from Google Cloud Console instead. For Microsoft Entra ID, enter your directory’s Tenant ID. Do not use 

common, organizations, or consumers because Raily cannot verify their placeholder issuer.For Custom, the issuer is the URL your provider serves /.well-known/openid-configuration from. Discover Config fills in the value the provider declares.Raily does not save the client secret in your browser while you work through the wizard. If you leave the wizard and come back, enter the Client Secret again.
4
Discover the OpenID configuration
Select Discover Config. Raily reads the provider’s OpenID configuration and fills in its authorization and token endpoints. Review the issuer if Raily updates its spelling, then select Continue.

5
Review the connection test and save
Raily tests the client credentials automatically when you continue. Confirm that Verify & Save says Connected and that the issuer and endpoints are correct.
Select Save.


Attach the provider to an endpoint
Adding a provider does not change any endpoint until you attach it.- When you create an endpoint, choose the provider under Who can connect. To change an existing endpoint, open it and choose the provider under Security → Sign-in provider.
- Select Create Server or Save Changes.
For an external provider, the endpoint page shows 1 step to go live with the endpoint’s redirect URL. Copy it, add it to the allowed callback URLs of the OIDC application in your provider, then select I’ve added it to mark the step done. Each endpoint has its own redirect URL. Raily-hosted sign-in does not need this step.

Next steps
Access control
Choose between user grants, external sign-in, and API keys
Add and manage users
Grant endpoints through Raily-hosted sign-in