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

[Joey Wang]

Hi, Scott,
The errors.xml file seems to only control the sub-status code:
Status:urn:oasis:names:tc:SAML:2.0:status:RequesterSub-Status:urn:oasis:names:tc:SAML:2.0:status:AuthnFailedMessage: An error occurred. The sub-status code urn:oasis:names:tc:SAML:2.0:status:AuthnFailed is configurable in errors.xml, but I could not find the status code (urn:oasis:names:tc:SAML:2.0:status:Requester) mapping in errors.xml. 
Thanks, Joey 

    On Tuesday, May 17, 2016 10:57 AM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
 

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



>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.

I thought you already found that part, that's controlled with the mappings in errors.xml

-- 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/b0f81728/attachment.html>