Feedback
Last date modified: 2026-Sep-01
Legacy authentication
Legacy authentication is the authentication workflow that RelativityOne used before Centralized Authentication. In this workflow, you create and configure each authentication provider individually using the New Authentication Provider button on the Authentication Provider tab.
These topics apply to instances that have not transitioned to Centralized Authentication. Both workflows are supported during the transition, so the steps you follow depend on which one your instance uses. For help identifying which setup applies to you, see Choosing your authentication setup.
If your instance uses Centralized Authentication, use Centralized Authentication instead. The provider setup steps in these topics do not match the fields in the Centralized Authentication wizard.
Legacy authentication providers
Review the topic for the identity provider you want to configure:
- OpenID Connect (legacy)—configure any identity provider that supports the OpenID Connect protocol, and set up just-in-time provisioning.
- Okta OpenID Connect (legacy)—configure Okta as an OpenID Connect identity provider.
- Microsoft Entra ID - OpenID Connect (legacy)—register an Azure application and configure Microsoft Entra ID as an OpenID Connect identity provider.
- SAML 2.0 provider (legacy)—configure a SAML 2.0 identity provider, including Okta and ADFS.
Assigning login methods
After you create an authentication provider, assign a login method to each user before that user can log in. For those steps, see Managing user authentication methods.
Related topics
See these related pages:
