diff --git a/src/pages/guides/authentication/ServerToServerAuthentication/implementation.md b/src/pages/guides/authentication/ServerToServerAuthentication/implementation.md index 15de37a9..3a71dcc6 100644 --- a/src/pages/guides/authentication/ServerToServerAuthentication/implementation.md +++ b/src/pages/guides/authentication/ServerToServerAuthentication/implementation.md @@ -17,14 +17,18 @@ Depending on the API or an Event to your project on the Adobe Developer Console, ### Credential Name -An admin in your organization can manage all OAuth Server-to-Server credentials by visiting the [Adobe Admin Console](https://adminconsole.adobe.com) > Users > API credentials. To find the correct API credential easily on the Admin Console, you can provide your OAuth Server-to-Server credential a name during credential setup. +When you set up an OAuth Server-to-Server credential in the [Adobe Developer Console](https://developer.adobe.com/console), you can give it a name. ![](../../../images/oauth-server-to-server-credential-name.png) -This name can be modified later in your project by visiting the OAuth Server-to-Server credential overview page. +This name can be modified later in your project by visiting the OAuth Server-to-Server credential overview page in the Developer Console. ![](../../../images/oauth-server-to-server-credential-name-update.png) +An admin in your organization can manage all OAuth Server-to-Server credentials by visiting the [Adobe Admin Console](https://adminconsole.adobe.com) (a separate portal from the Developer Console) under Users > API credentials. The name you set in the Developer Console is also shown in this list, so naming your credential makes it easier for an admin to find the correct one among all the API credentials in your organization. + +![](../../../images/oauth-server-to-server-credential-admin-console-name.png) + ### Selecting Product Profiles Depending on the API or Event you add, you may be asked to select product profiles to assign to your credential. These product profiles govern what data your application can/cannot access in your organization. diff --git a/src/pages/guides/authentication/UserAuthentication/implementation.md b/src/pages/guides/authentication/UserAuthentication/implementation.md index d3709272..3d55a548 100644 --- a/src/pages/guides/authentication/UserAuthentication/implementation.md +++ b/src/pages/guides/authentication/UserAuthentication/implementation.md @@ -136,10 +136,6 @@ The following samples demonstrate basic interaction with the Adobe OAuth endpoin - **Python Example** [Github repo](https://github.com/AdobeDocs/adobe-dev-console/tree/main/samples/adobe-auth-python) where you can find a complete Python based web app example that uses Adobe OAuth. -## OAuth 2.0 Playground - -The OAuth 2.0 playground allows you to test out the 3-legged OAuth flow and obtain access tokens for experimentation. Learn more about the playground [here](../Tools/o-auth-playground.md). - ## Further Reading There are several great resources to get more familiar with the OAuth2.0 framework - diff --git a/src/pages/guides/authentication/UserAuthentication/ims.md b/src/pages/guides/authentication/UserAuthentication/ims.md index 96b83fbd..d7489c87 100644 --- a/src/pages/guides/authentication/UserAuthentication/ims.md +++ b/src/pages/guides/authentication/UserAuthentication/ims.md @@ -416,4 +416,4 @@ Scopes for Experience Cloud user authentication based APIs APIs | Scopes ---|--- -Adobe Analytics | ```openid, AdobeID, read_organizations, additional_info.projectedProductContext, additional_info.job_function``` +Adobe Analytics | `openid, AdobeID, read_organizations, additional_info.projectedProductContext, additional_info.job_function` diff --git a/src/pages/images/oauth-server-to-server-credential-admin-console-name.png b/src/pages/images/oauth-server-to-server-credential-admin-console-name.png new file mode 100644 index 00000000..1aa31579 Binary files /dev/null and b/src/pages/images/oauth-server-to-server-credential-admin-console-name.png differ