Client branding "Customize OAuth2 parameters"

[NannaBarz]

WHAT Needs to be Documented?

For what exact do you need these parameters and how to set them (Oauth2, Azure wich is not possible to use dynamic client registration)

WHERE Does This Need To Be Documented (Link)?

I'm not sure if it should be in the branding docs or in the OpenID docs

WHY Should This Change Be Made?

It is possible to hard code the parameters with the ownBrander in the client

(Optional) What Type Of Content Change Is This?

• New Content Addition
• Old Content Deprecation
• Existing Content Simplification
• Bug Fix to Existing Content

(Optional) Which Manual Does This Relate To?

• Admin Manual
• Developer Manual
• User Manual
• Android
• iOS
• Branded Clients
• Desktop Client
• Other

@d7oc AFIAK you faced some issues here to get this work.

@mmattel

[michaelstingl]

@d7oc AFIAK you faced some issues here to get this work.

Related?

• Description of step 6 in Azure OIDC configuration could be improved #284

[d7oc]

Related?

• Description of step 6 in Azure OIDC configuration could be improved #284

This one was for the server configuration not client related.

[d7oc]

@d7oc AFIAK you faced some issues here to get this work.

The issues were about the missing feature to brand all OAuth2/OIDC parameters in some clients (I would use the term OIDC here as well as it might not be clear to everybody, that OIDC is based on OAuth2). We need all four parameters in the end (Client ID, Client Secret, OIDC Scopes and OIDC Prompt) for all clients.

I agree that this should be documented somewhere, I'm just not sure were this documentation should reside especially as this is not available to everyone.