-
Notifications
You must be signed in to change notification settings - Fork 484
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
Deployment configuration with authentication options #741
Comments
Hey @tewald. Could file a PR adding the changes? We're still in the process of discussing which authentication options to offer, especially given that we (Camunda) don't impose any constraints to our users. The two options you provide seem like two popular ones to go for. |
OK, my fault. |
Thanks for the PR. We'll merge it with one of our next releases. |
What's the state of this? |
Hi, Comunity is still waiting for this fix. Could you tell me, please, about your plans/future relases ? |
We cannot promise an exact availability date of this feature but rest assured this will land in one of the next Camunda Modeler releases. |
Closed via #906. |
Hi!
I'm using the dev version, testing the deploy functionality, and it works as expected.
But here our camunda rest API has a filter that uses JWT to set user and tenantId for the request.
So, to make it work, I added the Authentication header, with the bearer token, and it's all good again.
I think it should be nice to set some auth options, like in Insomnia REST client, for example.
I'm hacking some code here to add at least basic and token auth options to the configuration modal.
My JS-foo is not the strongest, but I did manage to do something like this:
What are you thoughts?
(On a side note, it could be nice to also load the diagrams from the rest api, making the modeler a full-online tool for camunda)
Thanks!
Thomas
The text was updated successfully, but these errors were encountered: