From 80437f0627ca9944eead2f2843303552b54bd5e4 Mon Sep 17 00:00:00 2001 From: alexandr cumarav Date: Tue, 21 Nov 2023 16:16:31 +0100 Subject: [PATCH] updating OIDC notes with Microsoft Entra ID support --- docs/extend/extend-apiml/api-mediation-oidc-authentication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/extend/extend-apiml/api-mediation-oidc-authentication.md b/docs/extend/extend-apiml/api-mediation-oidc-authentication.md index b036714e1d..4900d7980f 100644 --- a/docs/extend/extend-apiml/api-mediation-oidc-authentication.md +++ b/docs/extend/extend-apiml/api-mediation-oidc-authentication.md @@ -151,7 +151,7 @@ Check that the URL `jwks_uri` contains the key for OIDC token validation. :::tip**Tips** -API ML Gateway exposes a validate token `POST /gateway/api/v1/auth/oidc-token/validate` operation which is suitable during the OIDC setup. The Gateway expects JSON `{ token, serviceId }`. The call allows to verify that OIDC token is trusted by the API ML. The accounts mapping step is not included in that flow. +API ML Gateway exposes a validate token `POST /gateway/api/v1/auth/oidc-token/validate` operation which is suitable during the OIDC setup. The Gateway expects JSON `{ token, serviceId }`. The operation allows to verify that OIDC token is trusted by the API ML. The accounts mapping step is not included in that operation. ::: ## Azure Entra ID OIDC notes