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.

Sign up for GitHub

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

Jump to bottom

Keycloak Client post_logout_redirect_uri Support #157

Closed
SimplicityApks opened this issue Nov 19, 2022 · 3 comments
Closed

Keycloak Client post_logout_redirect_uri Support #157

SimplicityApks opened this issue Nov 19, 2022 · 3 comments
Assignees
@mikhailshilkov
Labels
kind/enhancement Improvements or new features resolution/fixed This issue was fixed

Comments

@SimplicityApks
Copy link

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Recent keycloak (>v19) has introduced the client parameter post_logout_redirect_uri specifying the valid URIs a client may redirect to after logout. See the logout docs.
It would be nice if pulumi gained support for this, as Keycloak by default does not allow any redirect. So in order for logout to work currently have to spam "+" into this field in every realm manually ;)

Affected area/feature
@SimplicityApks SimplicityApks added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team labels Nov 19, 2022
@guineveresaenger guineveresaenger removed the needs-triage Needs attention from the triage team label Nov 22, 2022
@guineveresaenger
Copy link
Contributor

Hi @SimplicityApks - thank you for filing this issue!

While we are awaiting upstream changes that will properly add this as an attribute to the Client resource, per that same upstream discussion, you should be able to leverage the ExtraConfig option to set this in the meantime.

@guineveresaenger guineveresaenger added the awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). label Nov 22, 2022
@maxemann96
Copy link

Just wanted to note, that the upstream issue is fixed. Can you please adjust the issue labels?

@mikhailshilkov mikhailshilkov self-assigned this Sep 23, 2024
@mikhailshilkov mikhailshilkov added resolution/fixed This issue was fixed and removed awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). labels Sep 23, 2024
@mikhailshilkov
Copy link
Member

Closing since the upstream issue was fixed a while ago

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mikhailshilkov mikhailshilkov

Labels
kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mikhailshilkov @maxemann96 @SimplicityApks @guineveresaenger