Skip to content
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

RedirectURI with same domain as issuer does not work #275

Open
CL1302 opened this issue Jan 17, 2025 · 3 comments
Open

RedirectURI with same domain as issuer does not work #275

CL1302 opened this issue Jan 17, 2025 · 3 comments
Labels
bug Something isn't working status:planned We plan to work on this

Comments

@CL1302
Copy link

CL1302 commented Jan 17, 2025

I don't find a way to authenticate via OpenID with PKCE Flow.
For example, the Client Secret field is a "must"-Field, but it's not necessary for PKCE.
I cannot find any option for that.

Is there another way to get it to work?
If not, it would be nice to support this flow in the future.

Thank you very much for this nice Tool!

@CL1302 CL1302 added the enhancement New feature or request label Jan 17, 2025
@latonz
Copy link
Contributor

latonz commented Jan 20, 2025

If you use a OAuth2 / OpenID-Connect auth configuration with a client authorization method of None, there shouldn't be a client secret field. The PKCE parameters are sent by default. Does this resolve your issue?

@CommonGuy CommonGuy added the status:needs-info To investigate this, more information is needed label Jan 20, 2025
@CL1302
Copy link
Author

CL1302 commented Jan 21, 2025

Thank you Lars!
Yes, the Client Secret Attribute is gone this way, but it doesn't work. When I update the Token, it should open a window of the IdP to authenticate I guess, but there is only an error below the Token-Field: "Unauthenticated".
Maybe we can check it together when we meet in person next time. If you like, you can close the issue. I can use another flow as workaround.
Cu, Christian

@latonz latonz changed the title Add support for PKCE Authentication RedirectURI with same domain as issuer does not work Jan 21, 2025
@latonz
Copy link
Contributor

latonz commented Jan 21, 2025

According to my analysis the oidc flow does not work in Kreya if the redirect uri is the domain of the issuer. The problem is not related to PKCE...
Not working example: Redirect uri: https://mycompany.com, Issuer: https://mycompany.com which leads to the authorization endpoint https://mycompany.com/authorize.

@latonz latonz added bug Something isn't working status:planned We plan to work on this and removed enhancement New feature or request status:needs-info To investigate this, more information is needed labels Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working status:planned We plan to work on this
Projects
None yet
Development

No branches or pull requests

3 participants