[keycloak-user] "Default" Client Template

[Jonas Schönenberger]

Hi Bill

Our clients are Oauth Clients that register dynamically and they expect
certain user information in the tokens. Is there a way to set default
mappers on realm-level until such a "client scope" feature is available?
Setting mappers manually (or apply templates manually) on each dynamically
registered client would kind of break the dynamic registration.

Thank you and Best Regards
Jonas


On Tue, Feb 6, 2018 at 7:04 PM, Bill Burke <bburke at redhat.com> wrote:

> No.  We will be doing work in this area soon.  I'm thinking of
> renaming templates to "Client Scope" and allow clients to inherit from
> multiple scopes  A client scope would only be able to specify allowed
> roles, groups, attributes and protocol mappers.  no other config
> option.  We would also do away with per-role and per-protocol mapper
> consent messages and instead allow the scope and/or client to define
> the consent message to give to the user.  All this to support the OIDC
> scope parameter better.
>
> I think a default scope would be an important addition.
>
> On Tue, Feb 6, 2018 at 8:15 AM, Jonas Schönenberger
> <jonas.schoenenberger at gmail.com> wrote:
> > Hi everyone
> >
> > Is it possible to define a default client template that every new dynamic
> > client (OpenID Connect Dynamic Client Registration) receives during
> > registration?
> >
> > Thank you for your help and Best Regards
> > Jonas
> > _______________________________________________
> > keycloak-user mailing list
> > keycloak-user at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/keycloak-user
>
>
>
> --
> Bill Burke
> Red Hat
>