From 3e1ec313684e02ec3a01e9159326d810636f18fc Mon Sep 17 00:00:00 2001 From: ckhened Date: Fri, 23 Aug 2024 16:38:17 -0700 Subject: [PATCH] Correction in README.md --- helm-charts/auth-apisix/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/helm-charts/auth-apisix/README.md b/helm-charts/auth-apisix/README.md index f9a14426b..4713f6619 100644 --- a/helm-charts/auth-apisix/README.md +++ b/helm-charts/auth-apisix/README.md @@ -72,7 +72,7 @@ export accessUrl=http://$NODE_IP:$NODE_PORT/
Apisix helm chart provides configs to change the service type to other options like LoadBalancer (apisix.service.type) and externalTrafficPolicy to 'local'(apisix.service.externalTrafficPolicy). These can be added in values_apisix_gw.yaml

-While accessing the published APIs, the HTTP Authorization header of the request should contain the Access token provided by Identity provider as 'Bearer \'

+While accessing the published APIs, the HTTP Authorization header of the request should contain the Access token provided by Identity provider as "Bearer <Access Token>"

The access token, refresh token, userinfo and user roles can be obtained by invoking OIDC auth endpoint through UI or token endpoint through curl and providing user credentials.

Below steps can be followed to get access token from keycloak and access the APISIX published ChatQnA API through curl