Flag to identify if user selected SSO or not

[Jeffrey Crawford]

Jeffrey <jeffreyc at ucsc.edu>

Both pilots and IT professionals require training and currency before
charging into clouds!
---------------------------------------

On Tue, Jun 7, 2016 at 10:53 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> > ​I thought of that but it doesn't help if it's the first SSO "thing"
> logged into.
> > Unless I'm missing something here.​
>
> No, I sort of forgot what you were trying to do, I was thinking about it
> from the point of view of what Scott was doing. You're right, that's not
> really the same thing.
>
> I guess there's a clear answer: I don't know how you're convincing it not
> to do SSO. If I knew that, I might have a better idea.
>

​Just using the supplied checkbox in the default IdP install. It's just
checked by default and a user must uncheck to participate in SSO (This was
due to worries of all the library and lab computers around campus).​


>
> The supported way of not doing SSO is to include a predicate that's
> attached to the authentication flow descriptor that controls seralization.
> It lets you tell it not to store the result of the flow for reuse later. If
> you were doing that, then the basic answer would probably be to apply that
> same logic in the attribute resolver.
>

​Is that the way it's done by the installed example?​


>
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160607/9b64a62c/attachment.html>