Client types #22263
Description
Description
Delivery of client types feature.
Related Github discussions for the reference:
Milestones/subtasks (just an idea, but we can clearify/update)
- Have things working with the basic client properties and with JSON client type provider. See Client types - milestone 1 #22262 for the details
- Admin console working for client screen (Read-only fields shown, but disabled for edit. Non-applicable fields hidden. Possibly some client tabs automatically hidden as well if there is nothing applicable to them)
- Basic CRUD of JSON client type provider working
- Like with client policies, it is not possible to CRUD built-in client types. But it should be possible to CRUD the JSON client types in a realm
- At this stage, we can have maybe only "JSON" view (Similar to Client Policies JSON view)
- Support for more advanced client properties (WebOrigins, RedirectUris, maybe roles, service-account roles, default/optional client scopes)
- Admin console "Form" view of client types (Depends on Milestone 3. Can be done with the help of UI team - we should likely involve UI team at least for design if not also for implementation of this)
- Integration with client type policy? At least have condition in client policies based on client-type, which would allow enforce some client policies for particular client types (can be useful for validations etc)
- Inheritance of client types. For instance "OIDC" client type can be ancestor of "Single page OIDC" client type and "Service account" client type
- Versioning of client types
- Java and Javascript client type
- Make client types out of preview. It may involve migration support (if we want to support the case when "type" is REQUIRED field for clients, we will need to migrate existing clients to some built-in type)
I think that some milestones might be done in paralel. For instance, it seems that milestones 2, 3, and 4 do not depend on each other and possibly can be worked in parallel.
Discussion
Motivation
No response