Open baalmael opened 1 year ago
Hi @baalmael ,
When adding a URL with authentication enabled, the deploy dialog should detect that authentication is required and add the Authentication options to the dialog.
The server does have to make a request first to check the endpoint and to verify. Can you confirm that these options do not appear for you, even after waiting for a few moments?
Hi @marstamm,
thank you! I replicated with a basic camunda engine project and there the feature works as you described. I will look into why our project behaves differently and come back to you.
Thank you for confirming. I'll close this issue for now, but feel free to reopen it when it is not working as intended
The issue was, that we had GET whitelisted which is why the modeler did not detect, that authentication is necessary for POST. I suggest using POST (the method that is needed to deploy model or start an instance) to check if authentication is necessary.
Independently I suggest to implement a way to enter authentication if a deploy/start instance request returned 401 (Unauthorized).
Thank you for getting back and great job on root-causing this! It makes total sense to be able to configure authentication even when only certain resources require authentication.
I'll reopen this ticket and move it into backlog.
Describe the bug
I know this was possible in earlier versions, but now this feature seems to be missing or is to hard to find.
Expected: I can deploy models using the modeler even when basic auth is enabled for the REST API.
Actual: -> Credentials do not match with the server. [ deploy-error ]
If this is still possible, the log could explain where to configure the credentials if putting the fields back into the deploy dialogue really is not possible.
Steps to reproduce
Expected behavior
Environment
Additional context
No response