You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I finished my prepwork to deploy Ory as an alternative to Keycloak to provide protection to my services as well as a centralized way of managing my users - or, to simply avoid having to create a new user for myself over and over again and use OIDC instead.
I have my DB configured and all the switches I want or do not want (or need). But unless I can tie it all together by linking the three services together, it'll not work. Oathkeeper, ment to protect my endpoints, is by far the most important part in this chain as I will use it as part of a Traefik middleware on some services that do not natively have authorization or alike (or just use a header passed downstream to re-use the authentication as in X-OIDC-User and alike).
Describe your ideal solution
Ideally, a simple table of option, default value and description would suffice.
Workarounds or alternatives
Not all options are documented in the charts' values.yaml. Adding all of them there first with some descriptive comments would be very nice.
Version
None, yet. I am targeting the latest Helm chart releases
Additional Context
None I can think of.
Thanks for this awesome project; I realized that some services I use daily had a "Powered by Ory" tag line. So I am very much looking forward to hosting it myself, too!
The text was updated successfully, but these errors were encountered:
Hello there!
The missing documentation for oathkeeper was a bug in the website, and it was not related to the charts repository, which is stored here.
Looking at the webpage, our devs managed to find and fix that bug 💪 and now you can again see all of oathkeeper config details there :)
I will close the issue, but if you have question regarding how to configure our apps/deploy them on k8s please feel free to ask it here: https://github.com/ory/k8s/discussions
Cheers!
Preflight checklist
Ory Network Project
No response
Describe your problem
I finished my prepwork to deploy Ory as an alternative to Keycloak to provide protection to my services as well as a centralized way of managing my users - or, to simply avoid having to create a new user for myself over and over again and use OIDC instead.
Well I was able to configure Kratos and Hydra so far - but, Oathkeeper...not so much. See: https://www.ory.sh/docs/oathkeeper/reference/configuration
I have my DB configured and all the switches I want or do not want (or need). But unless I can tie it all together by linking the three services together, it'll not work. Oathkeeper, ment to protect my endpoints, is by far the most important part in this chain as I will use it as part of a Traefik middleware on some services that do not natively have authorization or alike (or just use a header passed downstream to re-use the authentication as in
X-OIDC-User
and alike).Describe your ideal solution
Ideally, a simple table of option, default value and description would suffice.
Workarounds or alternatives
Not all options are documented in the charts'
values.yaml
. Adding all of them there first with some descriptive comments would be very nice.Version
None, yet. I am targeting the latest Helm chart releases
Additional Context
None I can think of.
Thanks for this awesome project; I realized that some services I use daily had a "Powered by Ory" tag line. So I am very much looking forward to hosting it myself, too!
The text was updated successfully, but these errors were encountered: