-
-
Notifications
You must be signed in to change notification settings - Fork 360
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
Unable to refresh RSA keys for JWK signing #53
Comments
Right, version 0.10.x works fine but a breaking change was introduced in 0.11.6 which changed the way JWK names are generated. Thus, oathkeeper doesn't work because it relies on the default key name generation which causes the 404. I'll dig into it and supply a fix! :) |
Sorry, this change will land in 1.0.0, it did not land in 0.11.0. I just ran the tests with v0.11.6 and it works, so it's either some fluke or misconfiguration in your environment. |
Thank you for your quick reply. I'v managed to move further and currently Oathkeeper raises the same error:
but Hydra complains:
When added
And finally:
So it seems the policy is not configured correctly (taken from here):
Could you please point me where an error could be? or maybe there is some another documentation which can explain me more. |
Right, it seems like the client definition is off:
should be:
|
Yeah, but unfortunately even using the correct client definition Hydra complains: And as I can understand the |
Right, seems like the create action is missing:
should be
ps: obviously, please replace the subject / resource ids :) |
Ok, now I see Hydra has granted access for oathkeeper-client user. But there is still an error in Hydra logs occurred while oathkeeper requests RSA keys for JWK signing:
I am sure the Attached stack if it may help: |
That might be due to some issues that occurred while you were testing. One possibility is to delete all keys from hydra related to oathkeeper, to use another key name (make sure to update the policy as well), or to recreate the database |
Now, it seems to unable find the key. The database was recreated.
|
Could you show the oathkeeper logs please? |
oathkeeper_1 | time="2018-03-01T12:54:33Z" level=info msg="Listening on :4456.\n" |
This is really confusing, it shows 500 in the one log, 404 in the other..can you please include the complete logs ( |
Having one 404 error is expected by the way, oathkeeper looks for the key first - if it doesn't find it it creates the key |
Sure, please see the logs: https://gist.github.com/taland/83557a97dc9b7ff261354c4d55aa9a6c Also I have added docker-compose.yml which I used for my test. |
It seems like it fails initially, but then works, see:
Also, it does not seem like oathkeeper fails again. What issue are you facing exactly? |
Yeah, right. Now it sorted. Thank you for your help with the policy definition. |
It would be awesome if you could update the docs - they are located here: https://github.com/ory/oathkeeper/tree/master/docs Thank you! Keeping this issue open until docs are improved |
Sure. |
This patch adds a GDPR compliant consent banner for cookies and Google Analytics: <img width="1904" alt="Bildschirmfoto 2020-11-06 um 11 37 19" src="https://user-images.githubusercontent.com/3372410/98357364-611b7400-2025-11eb-8a54-e23c8fc82f16.png"> When the user removes "Statistics", Google Analytics **will not be enabled**. Google Analytics is also **not enabled by default** which will imply a significant drop in reported users there. Closes ory#51
Hi.
I faced with an issue setting up Hydra in pair with OathKeeper. Following the guidelines I have run Hydra, but when I starting with OathKeeper it fails with an "Unable to refresh RSA keys for JWK signing" error.
Using:
OathKeeper log:
Hydra log:
Digging into the code of OathKeeper I found it depends on github.com/ory/[email protected]. And since it fails in the following line https://github.com/ory/oathkeeper/blob/master/rsakey/manager_hydra.go#L42 I did not find GetJsonWebKey method within JWKApi interface implemented for github.com/ory/[email protected]. It seems latest version of OathKeeper is incompatible with latest of Hydra.
Could you please advice what to do or probably share some drawbacks of using OathKeeper with latest version of Hydra?
Thanks in advance.
The text was updated successfully, but these errors were encountered: