Missing configuration related to activation flow

[Aravinda Liyanage]

Thank you Scott for the reply.

My thought process was that by using Actions, I wouldn't have to worry
about populating the context and parsing data from-to SAML etc.
Do you suggest ditching two AbstractAction class implementations altogether
and just use two servlets (original request handler and callback handler)
with `External` login flow?

Since, the workflow needs to be paused while redirects/internal
authentication process and no custom AuthenticationFlow is involved, is
there anything to do to preserve the context or it can be retrieved by
default using conversation key?


On Wed, Mar 26, 2025 at 3:21 PM Cantor, Scott <cantor.2 at osu.edu> wrote:

> > Does this sound like a feasible solution?
>
> No, that's totally unnecessary.
>
> The IdP already has an "External" login flow to bridge out to non-SWF
> logic, you don't have to do it yourself.
>
>
> https://shibboleth.atlassian.net/wiki/spaces/IDP5/pages/3199505369/ExternalAuthnConfiguration
>
> There are other integration paths possible with other login flows, but
> there's virtually no possibility implementing your own flow would make any
> sense this far along.
>
> -- Scott
>
>
>

-- 
Best Regards,
Aravinda Madushanka.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20250326/0e17a7c9/attachment.htm>