X509

[Vedran Bartonicek]

Hi,

At this point we are using LDAP for authentication.
It seems that we should also support X509 authentication - for clients that
are not using browser to access a protected resource.

Looking at
https://wiki.shibboleth.net/confluence/display/IDP30/X509InternalAuthnConfiguration
there is a note about:
"this flow doesn't redirect to a protected path; rather, the path of the
requested profile flow has to be protected, which typically will trigger as
soon as the client makes its first request. "

I don't get here what happens after client gets authenticated?
What mechanisms are in place (maybe something that is not part of
Shibboleth) to make sure that the authenticated client can then do
something (e.g. access some URL or something else)

-Vedran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160928/a97d9900/attachment.html>