-
-
Notifications
You must be signed in to change notification settings - Fork 37
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 do we set the redirect_uri #26
Comments
I am having the same issue. By setting a value in the database manually, it makes it work (so far, still working on implementing the whole flow) even without specifying it in the url |
/cc @jakkab |
According to https://github.com/ory/hydra-maester/blob/master/api/v1alpha1/oauth2client_types.go#L35 it's not possible to set |
@anshudutta |
As this case is about redirect_urls, which have been implemented by #30 already, should this case be closed and a new one opened to augment the CRD with all the stuff that is missing (see https://www.ory.sh/docs/hydra/sdk/api#schemaoauth2client for everything that can be set on a client)? @jakkab You said:
Is this a PR to augment the CRD with everything a oauth client in Hydra can have, or were you just talking about adding the redirect_urls? |
Hi @p-bakker , for other properties please create separate issue ;-) PR provided by @paulbdavis added |
Created #36 So I think this case can be closed now |
I have a kubernetes CRD like so
When I query a GET request to the admin server - http://hydra-admin:4445/client, I see two issues
redirect_uris
is nullclient_id
, that was passed is set asclient_name
This doesn't work because without setting the
redirect_uris
, hydra fails validation for oauth-client requestBut I could not find any way to set it.
I think the problem is that the current code is designed for grant type
client_credentials
even though it says that it is designed for all grant types. Because only that grant type doesn't need aredirect_uri
The text was updated successfully, but these errors were encountered: