Hi, we have evaluated the use of CAS 5 as an OAuth/OpenID connect server (we are already using CAS successfully for Web authentication, so this could be a natural extension).
The general OAuth/OpenID connect support works fine. However, I understand that the OAuth server support (as described in https://apereo.github.io/cas/5.0.x/protocol/OAuth-Protocol.html ) does not (yet) include the handling of scopes (e.g. to control the consent approval view, to control which services the user is allowed to access, to control which OIDC attributes are returned, to possibly store approvals / allow revocation of approvals). Are there any experiences in extending CAS to handle OAuth scopes? Are there plans to extend the general OAuth/OpenID support in this direction? Thanks in advance, best regards, Guido -- - CAS gitter chatroom: https://gitter.im/apereo/cas - CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html - CAS documentation website: https://apereo.github.io/cas - CAS project website: https://github.com/apereo/cas --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/trinity-23d3e2a3-726d-4f66-aa15-1a561f79aa43-1485184253323%403capp-gmx-bs04.
