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

oidcc_token:retrieve/3 returning {error,invalid_input,none} #408

Closed
GPrimola opened this issue Dec 16, 2024 · 1 comment
Closed

oidcc_token:retrieve/3 returning {error,invalid_input,none} #408

GPrimola opened this issue Dec 16, 2024 · 1 comment

Comments

@GPrimola
Copy link

oidcc version

3.2.6

Erlang version

27.1

Elixir version

1.17.3-otp-27

Summary

Couldn't update to 3.2.6 due to retro compatibility issues.
After a little dig, I could see the problem comes from here:

this on 3.2.6 adds {<<"code_verifier">>,none} to BodyQs, which makes uri_string:compose_query/1 to chain up the error {error,invalid_input,none}.

PS: this seems to work well on 3.2.5, but as I've strongly tested the auth flow on 3.2.4, I'm focusing on it.

Current behavior

After updating to 3.2.6 from 3.2.4 oidcc_token:retrieve/3 returns {error,invalid_input,none} when using with plug Oidcc.Plug.AuthorizationCallback.

How to reproduce

  1. Use an out of the box Keycloak with minimal configuration (realm, client and user);
  2. Configure Oidcc.Plug.AuthorizationCallback with following options set:
  • provider
  • client_id
  • client_secret
  • redirect_uri
  1. Perform the authorization flow (with redirect url)
  2. When on callback action, the plug will return {error,invalid_input,none} when trying to retrieve the token.

Expected behavior

oidcc_token:retrieve/3 on 3.2.6 should keep retro compatibility on patch versions, i.e., be able to return token information when the same parameters are given.

@GPrimola GPrimola added the bug label Dec 16, 2024
@maennchen
Copy link
Member

Duplicate of erlef/oidcc_plug#29

@maennchen maennchen marked this as a duplicate of erlef/oidcc_plug#29 Dec 16, 2024
@maennchen maennchen closed this as not planned Won't fix, can't repro, duplicate, stale Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants