Skip to content

Support keycloak custom format via configuration (backport #13216) #13259

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

Merged
merged 6 commits into from
Feb 13, 2025

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Feb 13, 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

This is an automatic backport of pull request #13216 done by [Mergify](https://mergify.com).

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

(cherry picked from commit 3041d6c)
(cherry picked from commit ecacf0f)
(cherry picked from commit bf7de92)

# Conflicts:
#	deps/rabbitmq_mqtt/test/auth_SUITE.erl
Fix test case nam# Por favor ingresa el mensaje del commit para tus cambios. Las

(cherry picked from commit aeda3ca)

# Conflicts:
#	deps/rabbitmq_mqtt/test/auth_SUITE.erl
@mergify mergify bot added the conflicts label Feb 13, 2025
Copy link
Author

mergify bot commented Feb 13, 2025

Cherry-pick of bf7de92 has failed:

On branch mergify/bp/v4.1.x/pr-13216
Your branch is ahead of 'origin/v4.1.x' by 3 commits.
  (use "git push" to publish your local commits)

You are currently cherry-picking commit bf7de92aa.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   deps/rabbitmq_mqtt/test/auth_SUITE.erl

no changes added to commit (use "git add" and/or "git commit -a")

Cherry-pick of aeda3ca has failed:

On branch mergify/bp/v4.1.x/pr-13216
Your branch is ahead of 'origin/v4.1.x' by 4 commits.
  (use "git push" to publish your local commits)

You are currently cherry-picking commit aeda3cada.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   deps/rabbitmq_mqtt/test/auth_SUITE.erl

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@michaelklishin michaelklishin merged commit 6064335 into v4.1.x Feb 13, 2025
1 of 2 checks passed
@michaelklishin michaelklishin deleted the mergify/bp/v4.1.x/pr-13216 branch February 13, 2025 01:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants