-
Notifications
You must be signed in to change notification settings - Fork 359
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 beta8 builds on older hydra SDK #101
Comments
Nice catch. There is a workaround though - as you don't need an access token to perform token introspection any more, it should be possible to omit those values and set the hydra_url to the admin port. Let me know if it works. This will be fixed anyways though! |
ps: And feel free to PR! |
PRs will abound, friend, but not before 15 days or so. Right now, I am getting it to work all together. Yes I found out too I should set the (deprecated) var HYDRA_URL to the admin port.
It does not work at all. When retrieving the keys, the proxy fails:
However, querying keys independently works: curl \
--location \
--header 'ContentType: application/json' \
--capath ./certs/mycorp-test.com/ca \
--get https://hydra.mycorp-test.com:4445/keys/oathkeeper:id-token
...
{
"keys": [
{
"kty": "RSA",
"kid": "private:ee0637f0-1530-4eb5-9d97-67ee9683813a",
"alg": "RS256",
"n": "****"
...
|
Omit |
ok at least it starts now thanks. |
Thanks! Let me know of any other difficulties. Upgrading to beta.8 SDK should solve this, but it should also be better documented that these values are not required usually. |
This patch improves compatibility with ORY Hydra 1.0.0-beta.8 and updates vendored dependencies. Closes #101 Signed-off-by: aeneasr <[email protected]>
This patch improves compatibility with ORY Hydra 1.0.0-beta.8 and updates vendored dependencies. Closes #101 Signed-off-by: aeneasr <[email protected]>
This patch improves compatibility with ORY Hydra 1.0.0-beta.8 and updates vendored dependencies. Closes #101 Signed-off-by: aeneasr <[email protected]>
This patch improves compatibility with ORY Hydra 1.0.0-beta.8 and updates vendored dependencies. Closes #101 Signed-off-by: aeneasr <[email protected]>
oathkeeper tag beta8 is not compatible with hydra beta 8.
In particular, this build uses pre-beta8 hydra SDK client, and is not able to distinguish AdminURL from PublicURL.
When running from docker images beta8 (hydra & oathkeeper), I am unable to have oathkeeper use a setup with admin and public running on separate ports.
The text was updated successfully, but these errors were encountered: