Skip to content

Support keycloak custom format via configuration#13216

Merged
michaelklishin merged 6 commits intomainfrom
issue-12324
Feb 13, 2025
Merged

Support keycloak custom format via configuration#13216
michaelklishin merged 6 commits intomainfrom
issue-12324

Conversation

@MarcialRosales
Copy link
Copy Markdown
Contributor

@MarcialRosales MarcialRosales commented Feb 7, 2025

Proposed Changes

Implements feature #12324

Docs pr:

Types of Changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

  • Bug fix (non-breaking change which fixes issue #NNNN)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause an observable behavior change in existing systems)
  • Documentation improvements (corrections, new content, etc)
  • Cosmetic change (whitespace, formatting, etc)
  • Build system and/or CI

That was not keycloak format it was an
extension to the oauth spec introuduced
a few years ago. To get a token from
keycloak using this format, a.k.a.
requesting party token, one has to specify
a different claim type called
urn:ietf:params:oauth:grant-type:uma-ticket
@MarcialRosales MarcialRosales marked this pull request as ready for review February 11, 2025 15:52
Fix test case nam# Por favor ingresa el mensaje del commit para tus cambios. Las
@michaelklishin michaelklishin merged commit fdaf16b into main Feb 13, 2025
@michaelklishin michaelklishin deleted the issue-12324 branch February 13, 2025 01:26
michaelklishin added a commit that referenced this pull request Feb 13, 2025
michaelklishin added a commit that referenced this pull request Feb 13, 2025
Support keycloak custom format via configuration (backport #13216)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants