Format: Native Spring
Legacy V2 File(s): conf/handler.xml
The authn/External login flow supports the use of an arbitrary external (to the IdP) authentication mechanism. Its basic function is to provide a non-WebFlow-based integration strategy for new authentication mechanisms. As a rule, using WebFlow is better, easier, and safer, but it does require writing Java code in most cases. This is usually true for external mechanisms also, but they can in some cases be implemented with JSP alone.
By default, the External flow is defined to lack support for advanced controls such as passive or forced authentication, but this can be changed in general-authn.xml or by copying the External flow to a new user-specified variant and changing its properties.
This login handler usually requires additional code be written in order to trigger the external authentication system. If you're simply looking to authenticate based on the presence of REMOTE_USER, refer to the RemoteUser flow.
Once control is transferred to the external path, the IdP has no control over what happens, and it will implicitly trust any information passed back through the defined interface. If that information can be manipulated, security holes may result. The deployer takes full responsibility for the security of the overall exchange.
Use conf/authn/external-authn-config.xml to configure this flow.
The shibboleth.authn.External.externalAuthnPath bean defines the flow redirection path to the resource that's used to perform the external login, by default a context-relative location. It can be modified if needed, but must be a resource with access to the container session. Modify as needed to match the location of your external interface (see the documentation on flow redirects).
As of V3.3, you may dynamically derive the path to use, typically so that it can vary based on aspects of the request, by defining a bean named shibboleth.authn.External.externalAuthnPathStrategy of type Function<ProfileRequestContext,String>.
The shibboleth.authn.External.ClassifiedMessageMap is a map of exception/error messages to classified error conditions. You can make use of this map either by modifying it to understand the error or exception messages returned by your external code, or by using the map as is and passing back the literal tokens in the map from your external code via the exception or error message interface.
The ExternalAuthentication class makes up the interface between the external code and the IdP. The general flow is:
- Call ExternalAuthentication.startExternalAuthentication(HttpServletRequest), saving off the result as a key.
- Do work as necessary (reading request details from the attributes below). Any redirects must preserve the key value returned in step 1 because it must be used to complete the login later.
- Set request attributes to communicate the result of the login back.
- Call ExternalAuthentication.finishExternalAuthentication(String, HttpServletRequest, HttpServletResponse). The first parameter is the key returned in step 1.
A trivial JSP implementation of this interface is below. This works as is, but is obviously quite limited in its behavior.
On first access to the external resource, the request attributes below will be set.
|ProfileRequestContext||Access to full request context tree|
|forceAuthn||Boolean||Whether the requester asked for re-authentication|
|isPassive||Boolean||Whether the requested asked for passive authentication|
|relyingParty||String||Name of the relying party requesting authentication|
|extended 3.2||Boolean||Whether this login flow has been invoked as an extension of another login flow|
|authnMethod (deprecated)||String||Identifier for an authentication method supported by the flow|
Use of "authnMethod" is deprecated because login flows in V3 are more general than in V2 and are designed to handle more than one possible method at a time, so the full semantics of a request can only be understood by examining the request context tree. The value in this attribute will generally be an arbitrary one chosen from among the possible set that the flow is configured to support. To determine whether the RP requested a specific form of authentication, you must walk the context tree from the root down to the AuthenticationContext and then on to a RequestedPrincipalContext.
|principalName||String||Name of authenticated subject to use as the login result|
|principal||java.security.Principal||Java Principal object to use as the login result|
|subject||java.security.Subject||Java Subject object to use as the login result|
|authnError||String||Error message to return in place of a successful login|
|authnException||Exception||Explicit exception object to return in place of a successful login|
|authnInstant||org.joda.time.DateTime||Exact time of authentication to report back|
|authnAuthorities 3.4||Collection<String>||Ordered collection of URIs identifying upstream/proxied authenticating "authorities" used to authenticate the subject|
If true, prevents the result from being saved for future use for SSO
|previousResult 3.3||Boolean||If true, the "new" AuthenticationResult is created with the "previousResult" flag set to true (mainly impacts auditing)|
Only one "result" or error attribute should be set by the external code. Setting more than one has unspecified behavior. In most cases, a simple principalName should be returned on success, but you can return the more complex objects to pass back additional information such as public or private credentials or custom principal data.
The beans defined in authn/external-authn-config.xml follow:
Spring Web Flow redirection expression for the protected resource
|shibboleth.authn.External.externalAuthnPathStrategy 3.3||Function<ProfileRequestContext,String>||A constant function returning the bean value above.||A function that returns the redirection expression to use for the protected resource|
|shibboleth.authn.External.ClassifiedMessageMap||Map<String,List<String>>||various||A map between defined error/warning conditions and events and implementation-specific message fragments to map to them.|
|An optional bean that can be defined to control whether to preserve the authentication result in an IdP session|
|shibboleth.authn.External.addDefaultPrincipals 3.2||Boolean||true||Whether to add the content of the |
|shibboleth.authn.External.matchExpression 3.3||Pattern||Regular expression to match username against|
This flow is designed to be similar to, but is not compatible with, the 2.x External login handler. In most cases, converting will be a matter of changing a bit of code to use new packages and APIs. The names of the servlet request attributes on input and output are largely compatible with V2.
Duplicating the Flow
If more than one instance of the external interface is needed to support different requirements, you can create any number of external flows by copying the descriptor in general-authn.xml, assigning a custom name to each copy, and creating a duplicate flow. For example, to create a custom version called "authn/ext1", copy files like so:
Obvious edits to both files are then needed to correct the paths and bean names used to configure the flow. You can create any number of such flows as desired.
Note that returning a Subject is often paired with setting the shibboleth.authn.External.addDefaultPrincipals bean to false, to dynamically establish Principal(s) representing the authentication method used without having them overwritten. For example, your External flow's
supportedPrincipals property might be defined to include both password and multi-factor authentication Principals (meaning it supports both methods), but you can return the specific method used at runtime in the Subject.