-
Notifications
You must be signed in to change notification settings - Fork 481
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
Add OAuth scope field to deploy modal #4102
Comments
We'd need zeebe-node to support passing a custom Shall I create an upstream issue @jwulf? |
@wollefitz Thanks for opening this issue! I buy into both the enhancement + proposed renaming. |
@nikku There's already camunda/camunda-8-js-sdk#21 (linked below "Additional Contect") created by Josh. |
Thanks @wollefitz. I'm a little bit confused as I don't care about camunda-8-js-sdk. We use the zeebe-node client and have not immediate intention to move to something else, unless explicitly required to do so. |
@nikku - with the 8.5.0 release we will be supporting the JS SDK. The Zeebe Node client published as zeebe-node is going to be unmaintained from 8.5.0. The new package will be @camunda8/zeebe. It’s the same code base, but moved to the camunda-8-js-sdk monorepo. |
Thanks for the heads-up @jwulf. |
Created #4109 from our end. Would be great to get a heads-up when It would help us if we'd get |
Waiting for upstream camunda-community-hub/zeebe-client-node-js#363 to be merged and released. |
* feat: support configuration of OAuth `scope` Related to camunda/camunda-modeler#4102 Implements camunda/camunda-8-js-sdk#21 * chore(types): `ZClientOptions#hostname` can be null Returned internally as `null`. * test: rewrite test cleanup Ensures we properly clean up after each test, also in cases of test failures. * Small tweaks * update CHANGELOG --------- Co-authored-by: Josh Wulf <josh.wulf@camunda.com>
Continuing to integrate this via #4169. |
* Rename `Audience` to `OAuth audience` * Add `OAuth scope` field Closes #4102
* Rename `Audience` to `OAuth audience` * Add `OAuth scope` field Closes #4102
This will be released with the next Desktop Modeler release ( |
Related to https://github.com/camunda/product-hub/issues/2089.
Problem you would like to solve
As a user, I want to be able to deploy to Zeebe clusters that use OAuth2 as authentication mechanism with a provider that requires a
scope
in the token request, e.g. Microsoft Entra ID.Proposed solution
Add a field "Scope" (or better "OAuth Scope" and rename "Audience" to "OAuth Audience") to the deploy modal which gets picked up by the Zeebe client for acquiring a token.
Alternatives considered
None
Additional context
scope
within the token request, see Support custom scope for tokens camunda-8-js-sdk#21Depends on camunda-community-hub/zeebe-client-node-js#363
The text was updated successfully, but these errors were encountered: