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

feat(acl): added a config always_use_authenticated_groups to support using authenticated groups even when an authenticated consumer exists. #13184

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

catbro666
Copy link
Contributor

@catbro666 catbro666 commented Jun 7, 2024

Summary

Currently, authenticated groups will only be used when there is no consumer or the consumer is anonymous. When there is an authenticated consumer, there is no way to use authenticated groups, only the groups associated with the consumer will be used.

This PR adds a config always_use_authenticated_groups to support using authenticated groups even when an authenticated consumer exists. If enabled, it will first try to use authenticated groups and will fallback to use the groups associated with the consumer if authenticated groups don't exist, which is consistent with the logic in the anonymous consumer case.

Checklist

  • The Pull Request has tests
  • A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
  • There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Issue reference

https://konghq.atlassian.net/browse/FTI-5945

@github-actions github-actions bot added core/clustering plugins/acl schema-change-noteworthy cherry-pick kong-ee schedule this PR for cherry-picking to kong/kong-ee labels Jun 7, 2024
@catbro666 catbro666 force-pushed the fti-5945-authenticated-groups-when-consumer-exists branch 5 times, most recently from d5f6aaa to 66e51d0 Compare June 11, 2024 03:22
…t using authenticated groups even when an authenticated consumer exists.

Currently, authenticated groups will only be used when there is no consumer
or the consumer is anonymous. When there is an authenticated consumer,
there is no way to use authenticated groups, only the groups associated
with the consumer will be used.

This PR adds a config `always_use_authenticated_groups` to support using
authenticated groups even when an authenticated consumer exists. If
enabled, it will first try to use authenticated groups and will fallback
to use the groups associated with the consumer if authenticated groups
don't exist, which is consistent with the logic in the anonymous consumer
case.

https://konghq.atlassian.net/browse/FTI-5945
@catbro666 catbro666 force-pushed the fti-5945-authenticated-groups-when-consumer-exists branch from 66e51d0 to eef8f21 Compare June 17, 2024 09: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.

None yet

1 participant