Local SSO integration with IdP 5.1.1

[Cantor, Scott]

> I'd  like to suppress this message in this case, but not sure the best way to
> accomplish that.

Nothing obvious, other than something hacky like creating a ScratchContext value, checking for it, and then clearing it, to guard the logic.

I'd probably go back and change my External servlet and have it signal a custom event by relying an exception or error message and mapping that with the classified messages feature into an event to signal so that it doesn't end up signaling NoCredentials.

Password is awkward because it has to loop, so it can't really tell when it's displaying for the first time or not.

-- Scott