OpenID Connect Client Config Needs more documentation #3

[jschristie]

nynymike commented on Mar 13

I think OpenID Connect client registration needs it's own documentation page. Customers are getting it wrong a lot.

Many of the parameters correspond directly to OpenID Connect client metatdata

There are a few configuration in the form that are specific to Gluu, like "Pre-Authorization."

Also, it may be worthwhile to have a section for "common config patterns" for
1.implicit clients ( response_type token id_token )
2.web clients ( response_type code )
3.mobile clients ( response_type code )

Also, helpful hints:
1.Use asymmetric crypto and no encryption when you pass the id_token to backend API's.
2.Use public identifiers (not pairwise) for trusted internal clients.

But we should review the support forums and find other common client config mistakes (especially specifying wrong response_types).

@nynymike nynymike added the enhancement label on Mar 13

@jschristie jschristie was assigned by nynymike on Mar 13

@willow9886

Add your reaction

Edit comment
Delete comment
Owner This user is the owner of the docs-3.0.1 repository.
willow9886 commented on Apr 4

@jschristie let's prioritize this... it's important that our openid connect functionality is properly documented.

Re-creating from old repo, since old repos are removed*********

[jschristie]

had been implemented in OpenID connect docs

https://gluu.org/docs/ce/3.1.1/api-guide/openid-connect-api/#parameters