-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: not getting the authorization token in header using openid-connect plugin #11220
Comments
What do you mean I'm trying to understand this issue, can you list details step by step? |
how we can get the user-information or jwt token from AD using openid-connect plugin it is setting the cookie in header but not setting the jwt token with this configuration |
i used the above config but i am expecting the usetdetails and. token as well in my header please let me know if i am doing anything wrong |
as per this docs it should come in header not sure what i am doing wrong @juzhiyuan |
Current Behavior
i am using openid-connect plugin,
it setting up the cookies into headers
expecting the authorization token in headers but its not setting it
{
bearer_only: false,
client_id: "XXXX",
client_secret: "SSSS",
discovery: "https://login.microsoftonline.com/xxxxxxxxxxx/v2.0/.well-known/openid-configuration", introspection_endpoint_auth_method: "client_secret_post",
realm: "master",
scope: "openid profile email",
set_access_token_header: true
}
let me know if i am missing anything
Expected Behavior
No response
Error Logs
No response
Steps to Reproduce
create a route
add the plugin openid-connect into the route
expecting the headers into the authorization
Environment
apisix version
):uname -a
):openresty -V
ornginx -V
):curl http://127.0.0.1:9090/v1/server_info
):luarocks --version
):The text was updated successfully, but these errors were encountered: