diff --git a/packages/@okta/vuepress-site/.vuepress/public/img/idp-logos/entraID.svg b/packages/@okta/vuepress-site/.vuepress/public/img/idp-logos/entraID.svg new file mode 100644 index 00000000000..0ed35fb73bc --- /dev/null +++ b/packages/@okta/vuepress-site/.vuepress/public/img/idp-logos/entraID.svg @@ -0,0 +1,9 @@ + + + + + + + + + \ No newline at end of file diff --git a/packages/@okta/vuepress-site/conductor.yml b/packages/@okta/vuepress-site/conductor.yml index c30a6fa8fa9..1d94c833d36 100644 --- a/packages/@okta/vuepress-site/conductor.yml +++ b/packages/@okta/vuepress-site/conductor.yml @@ -2391,6 +2391,10 @@ redirects: to: /docs/guides/add-an-external-idp/-/main/#next-steps - from: /docs/guides/add-an-external-idp/-/next-steps/index.html to: /docs/guides/add-an-external-idp/-/main/#next-steps + - from: /docs/guides/add-an-external-idp/azure/main + to: /docs/guides/add-an-external-idp/entra/main/ + - from: /docs/guides/add-an-external-idp/azure/main/index.html + to: /docs/guides/add-an-external-idp/entra/main/ - from: /docs/guides/sharing-cert/overview to: /docs/guides/sharing-cert/ - from: /docs/guides/sharing-cert/generate-new-credential diff --git a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/appidpinokta.md b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/appidpinokta.md deleted file mode 100644 index 7b3e04e9825..00000000000 --- a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/appidpinokta.md +++ /dev/null @@ -1,43 +0,0 @@ -* **Name**: Enter a name for the IdP configuration. -* **Client Id**: Paste the client ID that you obtained from Azure AD when you configured the IdP in the previous section. -* **Client Secret**: Paste the secret that you obtained in the previous section. -* **Scopes**: Leave the defaults. These scopes are included when Okta makes an OpenID Connect request to Azure AD. - - > **Note:** By default, Okta requires the `email` attribute for a user. The `email` scope is required to create and link the user to Okta's Universal Directory. - -In the **Endpoints** section: - -Add the following endpoint URLs for the Azure AD IdP that you’re configuring. You obtained these in the previous section. - -* **Issuer**: The identifier of the Azure AD IdP: `https://login.microsoftonline.com/{Directory(tenant)ID}/v2.0` -* **Authorization endpoint**: The URL of the Azure AD OAuth 2.0 authorization endpoint. For example: `https://login.microsoftonline.com/{Directory(tenant)ID}/oauth2/v2.0/authorize` -* **Token endpoint**: The URL of the Azure AD token endpoint for obtaining access and ID tokens. For example: `https://login.microsoftonline.com/{Directory(tenant)ID}/oauth2/v2.0/token` -* **JWKS endpoint**: The URL of the Azure AD JSON Web Key Set document. This document contains signing keys that are used to validate the signatures from the provider. For example: `https://login.microsoftonline.com/{Directory(tenant)ID}/discovery/v2.0/keys` - -In the optional **Authentication Settings** section: - -* **IdP Username**: This is the expression (written in Okta Expression Language) that is used to convert an IdP attribute to the app user's `username`. This IdP username is used for matching an app user to an Okta user. - - For example, the value `idpuser.email` means that it takes the email attribute passed by the IdP and maps it to the Okta app user's `username` property. - - You can enter an expression to reformat the value, if desired. For example, if the IdP username is `john.doe@mycompany.com`, then you could specify the replacement of `mycompany` with `endpointA.mycompany` to make the transformed username `john.doe@endpointA.mycompany.com`. See [Okta Expression Language](/docs/reference/okta-expression-language/). - -* **Filter > Only allow usernames that match defined RegEx Pattern**: Select this option to only authenticate users with transformed usernames that match a regular expression pattern in the text field that appears. This filters the IdP username to prevent the IdP from authenticating unintended users. - - > **Note:** When you use Okta for B2B or multi-tenancy use cases, select this checkbox. This helps you scope a subset of users in the org and enforce identifier constraints, such as email suffixes. - - For example, you could restrict an IdP for use only with users who have `@company.com` as their email address using the following expression: `^[A-Za-z0-9._%+-]+@company\.com`. - -* **Account Link Policy** > **Enable automatic linking**: Select this option for Okta to automatically link the user's IdP account with a matching Okta account. See [Account link](#account-link). - - When automatic linking policy is selected, and any validated OIDC JWT is provided, Okta searches the Universal Directory for a user's profile to link. The user profile is found when the **IdP username** value (email) passed by the IdP matches the **Match against** value (username). If there's a match, then the user is linked by mapping the required, static `sub` claim provided in the JWT to that user. - - After an account is linked, any validated JWT token with the same `sub` claim (which is mapped to the `idp.externalId` in the IdP profile) is automatically mapped to the same user. This happens regardless of the content of claims in the JWT. Also, the matching happens even if the values for **IdP username** and **Match against** no longer result in a match. - -* **Auto-link filters**: If the automatic linking policy is selected, you can configure linking to users in specific groups, exclude linking to specific users, and exclude linking to admin users. - - * **Include specific groups**: Include users in these groups for account linking. - - * **Exclude specific users**: Exclude these specific users from account linking. - - * **Exclude admins**: Exclude users who are assigned admin roles or have admin privileges from account linking. diff --git a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/createidpnote.md b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/createidpnote.md deleted file mode 100644 index 18c292f84b1..00000000000 --- a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/createidpnote.md +++ /dev/null @@ -1,3 +0,0 @@ -> **Note:** These steps configure Azure AD as the IdP with the OIDC protocol. To configure the connection with the SAML protocol, see [Make Azure Active Directory an Identity Provider](https://help.okta.com/okta_help.htm?type=oie&id=ext-azure-idp-setup). - -> **Note:** See the [Identity Providers API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider) for request and response examples of creating an IdP in Okta using the API. diff --git a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/idp.md b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/idp.md deleted file mode 100644 index b897814bf9a..00000000000 --- a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/idp.md +++ /dev/null @@ -1 +0,0 @@ -Azure AD diff --git a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/idpaccount.md b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/idpaccount.md deleted file mode 100644 index 8ab89bf9959..00000000000 --- a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/idpaccount.md +++ /dev/null @@ -1 +0,0 @@ -with [Azure AD](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) diff --git a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/accountlink.md b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/accountlink.md similarity index 100% rename from packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/accountlink.md rename to packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/accountlink.md diff --git a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/accountlinking2.md b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/accountlinking2.md similarity index 100% rename from packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/accountlinking2.md rename to packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/accountlinking2.md diff --git a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/afterappidpinokta.md b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/afterappidpinokta.md similarity index 100% rename from packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/afterappidpinokta.md rename to packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/afterappidpinokta.md diff --git a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/appatidp.md b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/appatidp.md similarity index 55% rename from packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/appatidp.md rename to packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/appatidp.md index 40df6e4b3c2..bb1835e7176 100644 --- a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/appatidp.md +++ b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/appatidp.md @@ -1,16 +1,20 @@ -1. Create an Azure AD app using these [instructions](https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app). +At the Microsoft identity platform, set up a tenant and register the client app that you want to use for authenticating and authorizing your users. -2. In the **Redirect URI** section of the page, paste the Okta redirect URI. The redirect URI sent in the authorize request from the client needs to match the redirect URI in the IdP. This is the URL where the IdP returns the authentication response (the access token and the ID token). It needs to be a secure domain that you own. This URL has the same structure for most IdPs in Okta and is constructed using your Okta subdomain and then the callback endpoint. +1. Set up a [Microsoft Entra tenant](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-create-new-tenant). - For example, if your Okta subdomain is called `company`, then the URL would be: `https://company.okta.com/oauth2/v1/authorize/callback`. If you’ve configured a custom domain in your Okta Org, use that value to construct your redirect URI, such as `https://login.company.com/oauth2/v1/authorize/callback`. +1. Register an [app in Microsoft Entra admin center](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app). + +1. In the **Redirect URI** section of the page, paste the Okta redirect URI. The redirect URI sent in the authorize request from the client needs to match the redirect URI in the IdP. This is the URL where the IdP returns the authentication response (the access token and the ID token). It needs to be a secure domain that you own. This URL has the same structure for most IdPs in Okta and is constructed using your Okta subdomain and then the callback endpoint. + + For example, if your Okta subdomain is called `company`, then the URL would be: `https://company.okta.com/oauth2/v1/authorize/callback`. If you've configured a custom domain in your Okta Org, use that value to construct your redirect URI, such as `https://login.company.com/oauth2/v1/authorize/callback`. Include all base domains (Okta domain and custom domain) that your users interact with in the allowed redirect URI list. -3. Copy the Azure application ID value so that you can add it to the Okta configuration in the next section. +3. Copy the **Application (client) ID** value so that you can add it to the Okta configuration in the next section. 4. Under **Certificates & secrets**, click **New client secret** to generate a client secret for your app. Copy the value so that you can add it to the Okta configuration in the next section. This is the secret that corresponds to your Azure application ID. - > **Note:** There may be other settings for the app that you can configure. The steps in this guide address the quickest route to setting up Azure AD as an IdP with Okta. See the Azure AD documentation for more information on other configuration settings. + > **Note:** There may be more settings for the app that you can configure. The steps in this guide address the quickest route to setting up Microsoft Entra ID as an IdP with Okta. See the [Microsoft Entra ID documentation](https://learn.microsoft.com/en-us/entra/identity/) for more information on additional configuration settings. For use in the next section, do the following: diff --git a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/appidpinokta.md b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/appidpinokta.md new file mode 100644 index 00000000000..59bbed7bd48 --- /dev/null +++ b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/appidpinokta.md @@ -0,0 +1,17 @@ +* **Name**: Enter a name for the IdP configuration. +* **Client Id**: Paste the client ID that you obtained from Microsoft Entra ID when you configured the IdP in the previous section. +* **Client Secret**: Paste the secret that you obtained in the previous section. +* **Scopes**: Leave the defaults. These scopes are included when Okta makes an OpenID Connect request to Microsoft Entra ID. + + > **Note:** By default, Okta requires the `email` attribute for a user. The `email` scope is required to create and link the user to Okta Universal Directory. + +In the **Endpoints** section: + +Add the following endpoint URLs for the Microsoft Entra ID IdP that you're configuring. + +* **Issuer**: The identifier of the Microsoft Entra ID IdP: `https://login.microsoftonline.com/{Directory(tenant)ID}/v2.0` +* **Authorization endpoint**: The URL of the Microsoft Entra ID OAuth 2.0 authorization endpoint. For example: `https://login.microsoftonline.com/{Directory(tenant)ID}/oauth2/v2.0/authorize` +* **Token endpoint**: The URL of the Microsoft Entra ID token endpoint for obtaining access and ID tokens. For example: `https://login.microsoftonline.com/{Directory(tenant)ID}/oauth2/v2.0/token` +* **JWKS endpoint**: The URL of the Microsoft Entra ID JSON Web Key Set document. This document contains signing keys that are used to validate the signatures from the provider. For example: `https://login.microsoftonline.com/{Directory(tenant)ID}/discovery/v2.0/keys` + + > **Note:** These URL values are obtained from the previous [Create an app at the Identity Provider](#create-an-app-at-the-identity-provider) section. diff --git a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/createidpnote.md b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/createidpnote.md new file mode 100644 index 00000000000..8edfaebd1a8 --- /dev/null +++ b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/createidpnote.md @@ -0,0 +1,3 @@ +> **Notes:** +> * These steps configure Microsoft Entra ID as the IdP with the OIDC protocol. To configure the connection with the SAML protocol, see [Make Azure Active Directory an Identity Provider](https://help.okta.com/okta_help.htm?type=oie&id=ext-azure-idp-setup). +> * See the [Identity Providers API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider) for request and response examples of creating an IdP in Okta using the API. diff --git a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/idp.md b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/idp.md new file mode 100644 index 00000000000..add8cbd828c --- /dev/null +++ b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/idp.md @@ -0,0 +1 @@ +Microsoft Entra ID diff --git a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/idpaccount.md b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/idpaccount.md new file mode 100644 index 00000000000..90e16a35044 --- /dev/null +++ b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/idpaccount.md @@ -0,0 +1 @@ +with [Azure](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) that has an active subscription to access the [Microsoft Entra admin center](https://entra.microsoft.com/) \ No newline at end of file diff --git a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/idpoption.md b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/idpoption.md similarity index 100% rename from packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/idpoption.md rename to packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/idpoption.md diff --git a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/useidpsignin.md b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/useidpsignin.md similarity index 100% rename from packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/azure/useidpsignin.md rename to packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/entra/useidpsignin.md diff --git a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/index.md b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/index.md index 52db846655b..597965c3ec3 100644 --- a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/index.md +++ b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/index.md @@ -7,7 +7,7 @@ meta: ## -This document explains how to configure as an [external Identity Provider](/docs/concepts/identity-providers/) for your application by creating an application at , creating an Identity Provider (IdP) in Okta, testing the configuration, and creating a sign-in button. +This document explains how to configure as an [external Identity Provider](/docs/concepts/identity-providers/) for your app by creating an app at , creating an Identity Provider (IdP) in Okta, testing the configuration, and creating a sign-in button. --- @@ -31,8 +31,6 @@ Okta manages the connection to the IdP for your app. The connection sits between ## Create an app at the Identity Provider -At the IdP, create the client application that you want to use for authenticating and authorizing your users. - ## Create an Identity Provider in Okta @@ -73,7 +71,7 @@ Alternatively, you can use the authorize URL to simulate the authorization flow. > **Note:** Use this step to test your authorization URL as an HTML link. For information on testing your authorization URL using the Sign-In Widget, Okta-hosted sign-in page, or AuthJS, see the [next section](#use-the-identity-provider-to-sign-in). > -> If you're using Authorization Code with PKCE as the grant type, you must generate and store the PKCE. See [Implement authorization by grant type](/docs/guides/implement-grant-type/authcodepkce/main/#flow-specifics). Okta recommends that you use the [AuthJS SDK](https://github.com/okta/okta-auth-js#signinwithredirectoptions) with this grant type. +> If you use the Authorization Code with PKCE grant type, you must generate and store the PKCE. See [Implement authorization by grant type](/docs/guides/implement-grant-type/authcodepkce/main/#flow-specifics). Okta recommends that you use the [AuthJS SDK](https://github.com/okta/okta-auth-js#signinwithredirectoptions) with this grant type. In the URL, replace `{yourOktaDomain}` with your org's base URL, and then replace the following values: diff --git a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/oktatookta/appatidp.md b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/oktatookta/appatidp.md index 6c6984af7e0..640509e5ae4 100644 --- a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/oktatookta/appatidp.md +++ b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/oktatookta/appatidp.md @@ -1,4 +1,4 @@ -When you're configuring federation between two Okta orgs, use OpenID Connect as the sign-in method: +In the Okta org that functions as the IdP, create a client app that you want to use for authenticating and authorizing your users. When you're configuring federation between two Okta orgs, use OpenID Connect as the sign-in method: 1. In the Admin Console for the Okta org that represents the IdP, go to **Applications** > **Applications**. 1. Click **Create App Integration**. diff --git a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/openidconnect/appatidp.md b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/openidconnect/appatidp.md index e41767cb0bb..90f3bfcc5dd 100644 --- a/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/openidconnect/appatidp.md +++ b/packages/@okta/vuepress-site/docs/guides/add-an-external-idp/main/openidconnect/appatidp.md @@ -1,4 +1,4 @@ -Use the documentation of the IdP to create a client application. +At the OpenID Connect IdP, create the client app that you want to use for authenticating and authorizing your users. Use the IdP's documentation to create a client app. You also need to add the redirect URI to the appropriate section. The redirect URI sent in the authorize request from the client needs to match the redirect URI in the OIDC IdP. This is the URL where the IdP returns the authentication response (the access token and the ID token). It needs to be a secure domain that you own. This URL has the same structure for most IdPs in Okta and is constructed using your Okta subdomain and then the callback endpoint. diff --git a/packages/@okta/vuepress-site/docs/guides/identity-providers/index.md b/packages/@okta/vuepress-site/docs/guides/identity-providers/index.md index 55be406a22c..c6b943e6bac 100644 --- a/packages/@okta/vuepress-site/docs/guides/identity-providers/index.md +++ b/packages/@okta/vuepress-site/docs/guides/identity-providers/index.md @@ -12,7 +12,7 @@ Not sure what an identity provider is? See [External Identity Providers](/docs/c ## Enterprise identity providers - Azure AD + Microsoft Entra ID Okta to Okta OpenID Connect SAML 2.0 diff --git a/packages/@okta/vuepress-site/docs/guides/social-login/main/index.md b/packages/@okta/vuepress-site/docs/guides/social-login/main/index.md index 8da5d88eabd..a1de1d75d6e 100644 --- a/packages/@okta/vuepress-site/docs/guides/social-login/main/index.md +++ b/packages/@okta/vuepress-site/docs/guides/social-login/main/index.md @@ -64,7 +64,7 @@ To remove an existing account link or validate account linking with every sign-i If **Account Link Policy** is disabled, no account linking occurs. You can manually create an account link without a transaction by making a `POST` call to the `/api/v1/idps/{idps}/users/{userId}` [endpoint](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProviderUsers/#tag/IdentityProviderUsers/operation/linkUserToIdentityProvider). -See [Add an Identity Provider](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider) for API examples of account linking JSON payloads. +See [Create an Identity Provider](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider) for API examples of account linking JSON payloads. For security best practices, consider disabling account linking after all existing users from the external IdP have signed in to your Okta org. At this point, all links have been created. After you disable linking, and JIT provisioning is enabled, Okta adds new users that are created in the external IdP. diff --git a/packages/@okta/vuepress-site/docs/guides/social-login/main/microsoft/appidpinokta.md b/packages/@okta/vuepress-site/docs/guides/social-login/main/microsoft/appidpinokta.md index defccd8eed7..4a8e0d52308 100644 --- a/packages/@okta/vuepress-site/docs/guides/social-login/main/microsoft/appidpinokta.md +++ b/packages/@okta/vuepress-site/docs/guides/social-login/main/microsoft/appidpinokta.md @@ -1,5 +1,5 @@ * **Name**: Enter a name for the Identity Provider configuration. -* **Client Id**: Paste the app ID or client ID that you obtained from the Identity Provider in the previous section. +* **Client ID**: Paste the app ID or client ID that you obtained from the Identity Provider in the previous section. * **Client Secret**: Paste the secret that you obtained from the Identity Provider in the previous section. * **Scopes**: Leave the defaults. diff --git a/packages/@okta/vuepress-theme-prose/assets/css/okta/icons/classes.scss b/packages/@okta/vuepress-theme-prose/assets/css/okta/icons/classes.scss index 6343f98c11f..00718352b7f 100755 --- a/packages/@okta/vuepress-theme-prose/assets/css/okta/icons/classes.scss +++ b/packages/@okta/vuepress-theme-prose/assets/css/okta/icons/classes.scss @@ -1997,10 +1997,10 @@ h1 { background-image: url("/img/icons/amazon-universal-gray-small.png"); } -.icon.azure::before { +.icon.entra::before { content: ""; - background-image: url("/img/icons/azure-ad-logo-75.png"); + background-image: url("/img/idp-logos/entraID.svg"); } .icon.discord::before { diff --git a/packages/@okta/vuepress-theme-prose/util/frameworks.js b/packages/@okta/vuepress-theme-prose/util/frameworks.js index 1bb1a2d5abe..f587657f51d 100644 --- a/packages/@okta/vuepress-theme-prose/util/frameworks.js +++ b/packages/@okta/vuepress-theme-prose/util/frameworks.js @@ -11,7 +11,7 @@ const FRAMEWORK_TO_COMMON_NAME = { const COMMON_NAME_TO_FANCY_NAME = { apple: 'Apple', - azure: 'Azure AD', + entra: 'Microsoft Entra ID', javascript: 'JS', angular: 'Angular', amazon: 'Amazon',