custom authentication

[Cantor, Scott]

> So, you mean that whatever this documentation is saying is internal to IDP
> and users shouldnot be using this?

You use it the way it's documented, by enabling that login flow and configuring the container to supply an identity to the configured resource path so it will be available by the time the IdP redirects the client to it. That doesn't include accessing that servlet directly under any circumstances.

There are exactly three supported protocols for invoking the IdP with a browser:

- CAS
- SAML 2.0
- Unsolicited SSO for SAML 1.1 or SAML 2.0

That's it. If you're not doing one of those things, you don't need this software. If you're doing something that doesn't involve a browser, there are some additional features, none of which have anything to do with your questions so I'm omitting them from the conversation.

-- Scott