PostAuthenticationFlows for non-SAML profiles

[Cantor, Scott]

On 8/20/15, 4:02 PM, "dev on behalf of Misagh Moayyed" <dev-bounces at shibboleth.net on behalf of mmoayyed at unicon.net> wrote:

>How does one define post-authentication flows for an IdP profile config that is not SAML based? Do I need to simply define getters/setters for those flows and the IdP would pick them up when that profile is activated, or is there more I need to do?

I think you're asking about the ProfileConfiguration beans? I defined a base interface called AuthenticationProfileConfiguration and that's where the getter is declared, and then I implemented it in the relevant SAML profile config classes.

But as far as making it get used, that's specifically wired into the relevant flows, with the set of intercepts to run pulled from the AuthenticationProfileConfiguration interface at runtime.

<bean id="PopulatePostAuthnInterceptContext"
            class="net.shibboleth.idp.profile.interceptor.impl.PopulateProfileInterceptorContext" scope="prototype"
            p:availableFlows-ref="shibboleth.AvailableInterceptFlows">
        <property name="activeFlowsLookupStrategy">
            <bean class="net.shibboleth.idp.authn.config.navigate.PostAuthenticationFlowsLookupFunction" />
        </property>
    </bean>

That bean uses a lookup function to populate the flows to run, and that function pulls from that interface.


Does that answer the question?

-- Scott