[JIRA] Closed: (SIDP-523) Add access to inbound AuthnRequest

[Chad La Joie (JIRA)]

     [ https://issues.shibboleth.net/jira/browse/SIDP-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chad La Joie closed SIDP-523.
-----------------------------

    Resolution: Fixed

added in rev 3072

> Add access to inbound AuthnRequest
> ----------------------------------
>
>                 Key: SIDP-523
>                 URL: https://issues.shibboleth.net/jira/browse/SIDP-523
>             Project: Shibboleth IdP 2 - Java
>          Issue Type: New Feature
>          Components: Authentication
>    Affects Versions: 2.3.3
>            Reporter: paulhethmon at idp.protectnetwork.org
>            Assignee: Chad La Joie
>            Priority: Minor
>             Fix For: 2.3.4
>
>
> Some relying parties I work with use the same EntityID for all of their applications. The only external difference in their requests is the ACS URL they pass in the AuthnRequest. The current Audit Log only logs the EntityID value and as such we cannot distinguish (for reporting purposes).
> Two ways I see to handle this:
> 1. Add the ACS URL to the current audit log
> 2. Expose the inbound AuthnRequest in the login context
> Option 2 is partially there in that the serialized version of the AuthnRequest is available in the SAML2LoginContext. Storing the actual object would be better so that the XML does not have to be processed multiple times.
> Option 2 would then allow a custom login handler access to all of the needed information. Option 1 would obviously negate the need for #2, but there may be other considerations for modifying standard files.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira