Forgot to add, there is still some more work planned for this:
- Better support for Audience parameter
- Convert roles to be added to the OIDC access token with the protocolMapper
- Improvements related to consent screen (ordering capability,
check/uncheck scopes)
- Scope parameter support for token exchange
- Groups support
- Client scopes inheritance
See the epic for more details:
https://issues.jboss.org/browse/KEYCLOAK-6600
If you have any ideas for improvements or if you find any
bugs/regressions caused by introducing clientScopes, feel free to reply
here or create JIRA and assign to me.
Thanks,
Marek
On 08/06/18 16:24, Marek Posolda wrote:
Thanks Bill, Vlasta and Matthew for the review and re-check
databases.
ClientScopes PR is in master as well as documentation is in docs
master. Summary of the changes in this old email:
http://lists.jboss.org/pipermail/keycloak-dev/2018-March/010528.html
Marek
On 05/06/18 16:22, Bill Burke wrote:
> I'll take a look this afternoon, my time.
>
> On Tue, Jun 5, 2018 at 6:49 AM, Marek Posolda <mposolda(a)redhat.com>
> wrote:
>> I've did a rebase of client scopes PR [1] against latest master. Also
>> did the documentation for it in the PR [2] .
>>
>> Anyone has a time to review? TBH I hope it's sorted soon as it changes
>> 291 files, so there is quite a chance for the conflict with every other
>> PR send. And rebasing (which I already did 2 or 3 times) is quite a
>> pain ;)
>>
>> [1]
https://github.com/keycloak/keycloak/pull/5076
>> [2]
https://github.com/keycloak/keycloak-documentation/pull/389
>>
>> Marek
>>
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
>