CAS Protocol Milestone

Cantor, Scott cantor.2 at osu.edu
Fri Aug 15 15:42:43 EDT 2014


On 8/15/14, 3:38 PM, "Marvin Addison" <marvin.addison at gmail.com> wrote:
>
>I considered making attribute resolution optional, but punted for
>simplicity. I may reconsider implementing as a profile configuration.

The one I mentioned on the call is the defaultAuthenticationMethods
setting, which may not be a CAS feature today, dunno, but somebody will
want it. I defined an AuthenticationProfileConfiguration interface to
carry it for non-SAML cases. It's really the only way to influence how
authentication happens if the protocol itself doesn't do it.

Well, not the only way, you can do it based on user identity also.

Anyway, I think it's worth maintaining the hook of a profile config object
because it's not much work and it's good for extensibility.

-- Scott



More information about the dev mailing list