# Identity Providers

Page description

This page explains how Identity Providers (IdPs) integrate with Revvy to enable Single Sign-On (SSO) and centralized authentication.

### Overview

The **Identity Providers** section allows organizations to configure external IdPs, such as Okta, Azure AD, Ping Identity, or any provider supporting **OpenID Connect (OIDC)**. Once configured, users can log in to Revvy using their enterprise credentials instead of creating separate accounts.\\

This improves security, simplifies user onboarding, and ensures consistent governance across enterprise systems.

### Viewing Identity Providers

After creating an Identity Provider, the **Identity Providers** list shows:

* **Name** of the IdP (e.g., Okta, Azure AD)
* **Status** (Active/Disabled)
* **Created** At timestamp
* **Updated** At timestamp\\

Each IdP entry represents a trusted authentication source for your Revvy tenant.

### Identity Provider Details

Clicking on a configured Identity Provider displays:

* **Basic Information:** Name, Type (e.g., OPEN\_ID)
* **OpenID Information:** Client ID, Client Secret, Issuer URL (provided by the IdP)
* **Button Information:** Custom text or logo displayed on the login page (e.g., “Login with Okta”)
* **Group Information:** Default group assignment for new users signing in through this IdP

### How It Works

1. An admin configures the IdP in Revvy using the details from their identity management system.
2. When users log in, they click the **SSO button** (e.g., “Login with Okta”).
3. Revvy redirects authentication to the IdP.
4. After successful login, the IdP passes the user’s identity back to Revvy.
5. The user is automatically placed into the configured default Group, inheriting its roles and permissions.

### Actions Available

From the detail page or action menu, admins can:

* **Edit** → Update IdP details (Client ID, secret, or group assignment)
* **Disable** → Temporarily stop authentication from this IdP
* **Delete** → Remove the IdP from the tenant

<figure><img src="https://599358484-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlcWbuZareqS9jci4Vs22%2Fuploads%2FvaFwfTNZjJJpBXS4NZqI%2Fimage.png?alt=media&#x26;token=873effd2-a8b3-43bc-941e-ab7d04aae577" alt=""><figcaption></figcaption></figure>

### Use Cases

* Enforcing **SSO** across the organization so users don’t manage separate Revvy credentials
* Ensuring compliance with **corporate security policies** (MFA, password rotation, etc.)
* Automatically mapping users to default groups for consistent **RBAC (Role-Based Access Control)**

### Best Practices

* Use descriptive names (e.g., “Okta-US”, “Azure-EMEA”) when managing multiple IdPs.
* Configure **Group mapping** carefully to ensure users inherit the right permissions.
* Periodically review and rotate the **Client Secret** provided by your IdP.
