Document configuration of the Identity SDK

[jonathanlukas]

Context

Slack Thread: https://camunda.slack.com/archives/C06EGD07V2N/p1705675145598509?thread_ts=1705661815.502959&cid=C06EGD07V2N

The Identity SDK should replace all component-specific identity integration configs (like Zeebe: https://docs.camunda.io/docs/self-managed/zeebe-deployment/configuration/gateway-config/#zeebegatewayclustersecurityauthenticationidentity). Here, please take in account that the link from the zeebe docs point to the identity application config, which is misleading.

This is documented ONLY in this section as of now: https://docs.camunda.io/docs/self-managed/platform-deployment/helm-kubernetes/guides/connect-to-an-oidc-provider/?optionsType=env

Goal

A reader is able to understand that each application requires an integration with identity to use features like multi-tenancy or resource-based permissions (everything that is not covered by oidc).

Proposal

Create a dedicated page that reflects the configuration of the identity SDK.

It could be located here:

• /Self-Managed/Identity/Deployment/Identity SDK
• /Self-Managed/Identity/Identity SDK/Configuration (allowing for more pages about the Identity SDK next to it)

[akeller]

This looks relatively large

The Identity SDK should replace all component-specific identity integration configs

Is there an epic driving this? @ultraschuppi

[jonathanlukas]

@akeller as I see it, the identity-sdk came up in the scope of oidc support: https://camunda.slack.com/archives/C06112NS4GJ