From 65792d8d6595bd32baf95da6cd84a93c3bc4ba03 Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Thu, 18 Dec 2025 06:16:20 +0000 Subject: [PATCH] Fix: Improve Azure AD Key Manager documentation --- .../administer/key-managers/configure-azure-ad-key-manager.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/en/docs/administer/key-managers/configure-azure-ad-key-manager.md b/en/docs/administer/key-managers/configure-azure-ad-key-manager.md index 02c5f9b9b2..4f3b3f937c 100644 --- a/en/docs/administer/key-managers/configure-azure-ad-key-manager.md +++ b/en/docs/administer/key-managers/configure-azure-ad-key-manager.md @@ -151,7 +151,7 @@ Start the API Manager server and log-in to the Admin portal to configure Azure A Scope Management Endpoint - The endpoint is used to manage the scopes. + The endpoint is used to manage the scopes.
Example:
https://<host>:9443/oauth2/scope Mandatory @@ -212,7 +212,7 @@ Start the API Manager server and log-in to the Admin portal to configure Azure A "description": "Access failure for API: /exampleapi/1.0.0, version: 1.0.0 status: (900901) - Invalid Credentials. Make sure you have provided the correct security credentials." } ``` - Please verify that the `iss` (issuer) claim in the token matches the issuer configured in the Key Manager Endpoints section. If there is a difference, update the issuer in the Key Manager Endpoints section to align with the `iss` value present in the token. + Please verify that the `iss` (issuer) claim in the token matches the issuer configured in the Key Manager Endpoints section. To obtain the `iss` value from the token, decode the JWT token (you can use tools like [jwt.io](https://jwt.io) or similar JWT decoder) and check the `iss` claim in the payload. If there is a difference, update the issuer in the Key Manager Endpoints section to align with the `iss` value present in the token. ### Post checks