-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
how to use hydra without "--dangerous-auto-logon"? #241
Comments
Please use
The secret is hashed in the rethinkdb table, that's why your access is denied. You must extract the client id and secret from the hydra logs as described here. |
Thanks. I know the logs contain client id and secret when running with docker, but I used binary hydra which only print the following message: INFO[0000] DATABASE_URL set, connecting to RethinkDB. So, I have to look up rethinkdb tables for the client id and secret. The client id is correct, the secret is hashed or crypted, cannot pass the check in access_request_handler.go:
|
It should not matter if you use hydra from source or binary. The client credentials will always be printed. It looks to me as if you are connecting to existing hydra tables in rethink db. On existing hydra installations (hydra checks if it already connected to your database in the past) the client is not regenerated and thus not printed to logs.
Yes, the secret is being hashed which is why you can't look it up in rethink. |
Thank you! The problem is solved. I delete the database, then everything works as expected. |
Glad to hear that! |
When I started hydra with '--dangerous-auto-logon', the oauth2 will work properly. When I start hydra without that option, both the cli and the http request failed with the same error message:
The start command is:
When connecting to hydra, I tried:
1, run "hydra clients create --skip-tls-verify" with or without CLIENT_ID, CLIENT_SECRET env;
2, try the http request with the correct client_id:
The settings are:
1, ".hydra.yml" contains the correct 'cluster_url', the client_id and client_secret come from rethinkdb table 'hydra_clients';
2, rethinkdb table 'hydra_json_web_keys' has 4 pairs of keys: hydra.tls, hydra.openid.connect, consent.endpoint, consent.challenge;
I had read the document several times, didn't know what I did wrong.
I use the binary hydra 0.4. The full error message is:
The text was updated successfully, but these errors were encountered: