-
-
Notifications
You must be signed in to change notification settings - Fork 358
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
oathkeeper Authorizers handler can not receiving values from the AuthenticationSession Header #512
Comments
Thank you for contributing to this repository by creating an issue! Unfortunately, your issue lacks vital information, such as log files, the error message, the software version, your configuration or other pieces of the puzzle. Please also ensure that your issue is appropriately formatted. If you do not know how to write markdown, you can find help here. Helping you with your problem is only possible if you share this information, and it will save a lot of time of back and forth on your as well as our end! For this reason, this repository uses issue templates which you can select when pressing "New issue". Please use one of those issue templates to fill in the required information. You can either create a new issue for this purpose and close this one, or leave a comment.
If you do not provide the requested information, this issue will be closed. |
Thank you for opening this issue. It appears that the request for more information (e.g. providing the software version, providing logs, ...) has not yet been completed. Therefore this issue will be automatically |
I can reproduce the issue:
oathkeeper config like this:
This is the application:
As i've remoted kratos here in this example it's fine that subject and probably clientID is empty but header should be filled.
|
@k9ert That's my understanding as well. I've checked it as well, and when trying to use the
Gives following results:
|
Hm, I think header is a map string interface, so maybe you have to do some printf? |
I did something like this:
receiving:
|
Thank you for opening this issue. It appears that the request for more information (e.g. providing the software version, providing logs, ...) has not yet been completed. Therefore this issue will be automatically |
"authorizer": {
"handler": "remote_json",
"config": {
"remote": "http://192.168.124.18:4000/authz/permission/allow",
"payload": "{"subject": "{{ print .Subject }}", "url": "{{ print .MatchContext.URL}}","clientId": "{{ print .Extra.client_id }}","method": "{{ print .Header }}" }"
}
},
payload : subject ,url, clientId,is ok, but the method value from Header is empty .
The text was updated successfully, but these errors were encountered: