Open Ben-Sheppard opened 2 weeks ago
@Ben-Sheppard is this something you and the Identity team will deliver? Or are you looking for technical writing support to deliver?
We're pretty focused at the moment on delivering features in the new streamlined architecture so it would be great to get support from our technical writers :) - I'm happy to support if that would be of use
@conceptualshark getting this on your radar. If you have enough info between the description and the linked ticket, you can draft a PR and have @Ben-Sheppard review.
Alternatively, you can make incremental improvements with this issue, and open a new issue with the remaining scope.
Related issues
https://jira.camunda.com/browse/SUPPORT-22349
Description
As part of the investigation into the linked support request, it was spotted that the docs relating to the configuration steps and setup for OIDC connections isn't consistent between
Generic
andMicrosoft Entra
.To reduce confusion, and create a better experience, these docs should be aligned. The
Generic
tab produces the correct outcome which is that there is an app registration for each component in the Camunda stack that you wish to connect and not one app registration for the entire stack.We should also take this opportunity to add a note in the
Component specific configuration
section that Web Modeler requires two clients, one for the Internal API and one for the External/Public API.