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
Following the "Using a locally available binary" steps, I've copied the commands listed verbatim. This is the output:
$ hydra clients create \
> --endpoint http://localhost:4445 \
> --id test-client \
> --secret test-secret \
> --response-types code,id_token \
> --grant-types refresh_token,authorization_code \
> --scope openid,offline \
> --callbacks http://127.0.0.1:4445/callback
You should not provide secrets using command line flags, the secret might leak to bash history and similar systems
OAuth 2.0 Client ID: test-client
$ hydra token user \
> --endpoint http://localhost:4445/ \
> --scope openid,offline \
> --client-id test-client \
> --client-secret test-secret
Setting up home route on http://127.0.0.1:4446/
Setting up callback listener on http://127.0.0.1:4446/callback
Press ctrl + c on Linux / Windows or cmd + c on OSX to end the process.
If your browser does not open automatically, navigate to:
http://127.0.0.1:4446/
When I click the Authorize application link on that webpage, I get the error 404 page not found, with the following output in the Hydra log:
Updates README to fix inconsistencies between Docker commands and local binary commands.
Closes#10
Signed-off-by: Marcel de Graaf <mail@marceldegraaf.net>
Following the "Using a locally available binary" steps, I've copied the commands listed verbatim. This is the output:
When I click the
Authorize application
link on that webpage, I get the error404 page not found
, with the following output in the Hydra log:Can you help me understand what's going wrong here? Thanks!
The text was updated successfully, but these errors were encountered: