authn/noop flow?

[Cantor, Scott]

On 2/3/17, 3:49 PM, "dev on behalf of Scott Koranda" <dev-bounces at shibboleth.net on behalf of skoranda at gmail.com> wrote:
    
>    Ah, yes. I will go look at that in detail again.

Possible caveat is that I think it has to perform a lot of logic that the default function is doing to keep things working like they should so it might be a little low-level for routine use. It's definitely more amenable to Java and not a script.

Arguably, the use case you mentioned is really one for the IPAddress flow itself. If you controlled it sufficiently, couldn't you attach the right context class principal to that flow and just have your rule run that flow to essentially *be* a no-op?

I guess one problem with that is that it produces a UsernamePrincipal that would collide with the Password flow. You'd still end up needing a custom merge to strip that dummy username out or it would cause hassle downstream. Would be easy to maybe add an option to the IPAddress flow to control whether to include that principal. Might be more useful than a truly no-op flow.

-- Scott