https://www.ory.com/ logo
Join Slack
Powered by
Hey, is there a way to skip the consent screen on ...
# talk-hydra
b
Hey, is there a way to skip the consent screen on a self hosted installation?
w
h
See also 
skip_consent
in the API docs, since hosted Hydra doesn’t have a UI.
b
Thanks for the response @handsome-agency-20541
I am getting an error that I can’t figure out
“error_description”: “The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed. Make sure that the various parameters are correct, be aware of case sensitivity and trim your parameters. Make sure that the client you are using has exactly whitelisted the redirect_uri you specified.”
But I did register the client with that redirect_uri
BTW I also added the skip_consent but it still navigates to the consent page, I worked around it by accepting it and just redirecting
@handsome-agency-20541 Any ideas regarding the redirect_uri error message?
h
I’m sorry, can’t put my finger on anything. https://www.ory.sh/docs/reference/api#tag/oAuth2/operation/oauth2TokenExchange mentions 
error_debug
callback parameter being available in debug mode. Try enabling it (can’t say how exactly though).
b
trying now
But I am already running in dev mode
And I cant see an error 😢
tried this as well
Is there any way to debug this or anyone can help?
@wide-dawn-74672 @handsome-agency-20541 any advice?
h
Nope, sorry. I have only a bit of experience with Ory Network, and none with self-hosted Hydra.
w
I'll gonna setup hydra self hosted in the next days with skip consent option, will keep you updated
b
Thank you 🙏 Im trying to debug it for now
m
Hello @bright-accountant-54540 what version are you running? AFAICT the feature is only on master and not yet properly released.
w
It would really help if the docs are versioned as well, have come across features in the docs that aren't released yet
m
Hey Chris, we did have versioned docs in the past, but it was a ton of work to keep them in sync. We also found on usage metrics that almost everyone is on the latest version and almost noone is using the versioned docs outside of the API reference. At the moment Ory Network is always on the latest version and backwards compatible. We still have to find a good way to somehow “mark” features that are not yet properly released on github. I am thinking maybe a flag in docusaurus that points this out on the relevant feature pages. But there is probably no super easy solution. @thousands-vase-40385 @wonderful-lamp-2357 fyi lets think a bit about how we can solve this in the near future?
w
@magnificent-energy-493 That 100% makes sense but I think it would be a good addition to not show features in documentation that aren't properly released yet 🙂
m
I mean they are released on Ory Network and are on master and should generally work also for self-hosting. But a notice to point this out to self-hosting users would be great 👍
w
Thanks for clarifying @magnificent-energy-493 👏
b
Hey guys sorry I didn’t reply and thank you all for the help
I managed to resolve this
Hydra v2.0.3
My issue was that I was trying to use the wrong grant
Yeah we noticed a while ago that the version documentation was removed and we try to keep all of the services up to date
I think that it will help people in the future if the error messages are more clear, because I was looking in the wrong place for a while, I read the docs for like 2 days now 😂 . When I got this error message it was like it defaults to it
Anyway thanks so much I really appreciate the replies ❤️
10 Views
Open in Slack
PreviousNext
Powered by