Enrich SAML & OpenID Connect client metadata

[NicolasLiampotis]

The client metadata should be enriched to include additional information about the client such as: logo_uri - OPTIONAL. URL that references a logo for the Client application. If present, the server SHOULD display this image to the End-User during approval. The value of this field MUST point to a valid image file. If desired, representation of this Claim in different languages and scripts is represented as described in Section 2.1. policy_uri - OPTIONAL. URL that the Relying Party Client provides to the End-User to read about the how the profile data will be used. The value of this field MUST point to a valid web page. The OpenID Provider SHOULD display this URL to the End-User if it is given. If desired, representation of this Claim in different languages and scripts is represented as described in Section 2.1. tos_uri - OPTIONAL. URL that the Relying Party Client provides to the End-User to read about the Relying Party's terms of service. The value of this field MUST point to a valid web page. The OpenID Provider SHOULD display this URL to the End-User if it is given. If desired, representation of this Claim in different languages and scripts is represented as described in Section 2.1.

See also https://openid.net/specs/openid-connect-registration-1_0.html

[cgeorgilakis]

This and related issue can be implemented with changes only to theme - if Keycloak team refuse/ delay to accept PRs. We only will not be able to import these fields with dynamic Client registration and validate URLs.

[cgeorgilakis]

PR : https://github.com/keycloak/keycloak/pull/8082 Keyclaok jira issue : https://issues.redhat.com/browse/KEYCLOAK-18268

[cgeorgilakis]

Merged into issue#87