Support custom scope for tokens #21
Assignees
Milestone
Comments
nikku
added a commit
to nikku/zeebe-client-node-js
that referenced
this issue
Feb 29, 2024
nikku
added a commit
to nikku/zeebe-client-node-js
that referenced
this issue
Feb 29, 2024
jwulf
added a commit
to camunda-community-hub/zeebe-client-node-js
that referenced
this issue
Mar 1, 2024
* 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 <[email protected]>
|
It has been added for the components that use the shared OAuth component (all clients except the Zeebe client). The next step is to either: (a) port the scope threading to the Zeebe client in this repo; or |
|
The Zeebe client now uses the shared OAuth component. See this PR: #46 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SDK Component
OAuth component, and Zeebe client (if it doesn't use the OAuth component)
Expected Behavior
Has the ability to specify the token scope via env var and constructor to support custom identity providers. See: camunda/camunda-modeler#4102
Current Behavior
OAuth hardcodes the scopes per component.
The text was updated successfully, but these errors were encountered: