How to generate event in authn flow to map to SAML status

[Joey Wang]

 Hi, Scott,
I noticed the top-level SAML status code returned to SP seems always "urn:oasis:names:tc:SAML:2.0:status:Requester". Is this field configurable? In some cases, our module may want to return other status code such as urn:oasis:names:tc:SAML:2.0:status:Responder.
Thanks, Joey

    On Monday, May 16, 2016 3:00 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
 

 On 5/16/16, 1:52 PM, "dev on behalf of Joey Wang" <dev-bounces at shibboleth.net on behalf of carbon_60 at yahoo.com> wrote:



>I am writing an authn flow extension and my question is how I can raise the event "InvalidCredentials" in my extension? Is there an example that I can follow?

The end-state that a login flow terminates with eventually gets "rippled" out of the stack of flows calling each other and becomes the event that gets processed as an error.

The built-in events, like that one, are already defined in an abstract parent flow that all the login flows should inherit from, there's an <end-state id="InvalidCredentials"/> defined. So if your flow signals that event, it will automatically happen.

-- Scott

-- 
To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net


  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20160517/841ef8ea/attachment.html>