-
-
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
docs: followed the installation guide and was unable to get a successful consent #623
Comments
Hey, I found the error, it's a typo here:
specifically
that line should read
|
Hey, and this removed the follwing error:
It seems there are many breaking changes in the new 0.10 and you stated in the change log that I think it warrants a re-write of the installation guide to better explain the concepts. |
Oh yes absolutely! Would you mind updating that in the consent app as well? Thank you so much for this, you are helping a lot of people! |
no problem. I wanted to find out where hydra stores its core scopes as I didn't find them in the database, and if I could pick your brains a little to better understand the system when I have question, I would like to write a documentation detailing this and we could publish it if you wanted. |
The scopes are stored in this SQL column - and I always welcome docs! :) |
I mean, how does hydra know about hydra.consent ? |
I hope all your questions are answered and thus closing this issue. If questions remain feel free to come back here. |
Hello,
I followed the installation guide
https://ory.gitbooks.io/hydra/content/install.html#perform-oauth-20-flow
and was unable to get a successful run.The issue seems to come from consent app saying
Unhandled rejection Error: Bad Request
and
From hydra
level=error msg="An error occurred" error="The client is not allowed to request scope hydra.consent: The requested scope is invalid, unknown, or malformed"
i have also noticed different versions in the guide so on my last attempt I used the version
v0.10.0-alpha.8
for:I noticed that this gave me an extra migration that was not available in the v0.9.x so I thought this might have been a mistake in the guide.
I will try to diagnose the issue further to see where the complain is from and dig deeper.
Thank you.
The text was updated successfully, but these errors were encountered: