Firstyear
Firstyear
> Idk what to do with the conflicting files lol I think those are the prebuilt items, so a rebase + wasm build then git add ; git rebase --continue...
@johanfleury It happened because oauth2 client credentials were merged, which necessitated turning oauth2 clients into "accounts". Because of that the oauth2_rs_name now became "name" and can potentially conflict with other...
Yes it is - this is because group names *might* change so it's safer to use the stable identifier. I have considered that we provider both uuid *and* spn though...
Custom claims are in the next release/version of the server. I will add the spn support shortly.
> I see. However IMHO for the resource server namely the names are of more value -- similar to DNS which translates human-friendly names to opaque machine ids -- application...
I think in this case, it's okay to expose the groups by spn here. So I'll close it once I add that quickly.
> The rationale is that the the `groups` claim may grow and easily exceed the cookie allowed length, in case when extensive grouping used. You could hit that anyway, which...
We can do what we did for usernames, and show name if present, or spn if not.