-
Notifications
You must be signed in to change notification settings - Fork 602
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
Oauth2 Scope is not exposed in Zeebe SDK config #23071
Labels
component/zeebe
Related to the Zeebe component/team
kind/toil
Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc.
version:8.6.1
Comments
megglos
added
kind/toil
Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc.
component/zeebe
Related to the Zeebe component/team
labels
Oct 4, 2024
3 tasks
github-merge-queue bot
pushed a commit
that referenced
this issue
Oct 10, 2024
## Description Exposes OAuth scope property in sdk config. ## Checklist <!--- Please delete options that are not relevant. Boxes should be checked by reviewer. --> - [ ] for CI changes: - [ ] structural/foundational changes signed off by [CI DRI](https://github.com/cmur2) - [ ] [ci.yml](https://github.com/camunda/camunda/blob/main/.github/workflows/ci.yml) modifications comply with ["Unified CI" requirements](https://github.com/camunda/camunda/wiki/CI-&-Automation#workflow-inclusion-criteria) ## Related issues closes #23071
This was referenced Oct 10, 2024
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
component/zeebe
Related to the Zeebe component/team
kind/toil
Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc.
version:8.6.1
Description
A clear and concise description of what this issue is about. The OAuth scope which can be configured on the zeebe client via the env var
ZEEBE_TOKEN_SCOPE
is not exposed via the config of the spring sdk. For alignment it should be available for configuration, like other auth properties (clientId, secret etc.) too.Tasks
Workaround:
The current workaround is to set the env var ZEEBE_TOKEN_SCOPE.
The text was updated successfully, but these errors were encountered: