Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upDocs: reference configuration provides invalid bcrypt cost and some other outdated values #2077
Comments
|
Right, we auto generate the page you are referring to. It is not really an example you can use but it documents all the possible values. We should actually add more specific validation (looks like range (4,31) would do the trick) to the bcrypt values. Then the rendered values will also be valid. But for the deprecation warning, it is because the config reference documents all keys and therefore also the deprecated ones. You will be better off using the quickstart config |
|
@vinckr I think it is a good task for you.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


I've following the various docs in an attempt to run Ory Hydra using the binary, and I've used the reference configuration from
docs/docs/reference/configuration.mdin order to speed up the setup of a basic playground.On one hand, there seems to be a few outdated values in that reference configuration as per the following warning messages:
On the other hand, I got the following 500 error when invoking the create an OAuth2 client endpoint (when sending a correct POST payload):
While in retrospective the error is somehow obvious, at the time of debugging I spent a non trivial amount of time and tons of googling to realize that the offending value came from the config.yaml I was using.
Reproducing the bug
Steps to reproduce the behavior:
Expected behavior
IMHO it would be a bit more useful and less error prone to have a valid value for the bcrypt cost setting, for example using the recommended/default value of
10as per the config comments.Environment