IdP 3 and Stale Requests
James Gross
JamesGross at uncc.edu
Tue Nov 17 09:47:29 EST 2015
Scott,
Just as an update. It appears that these were occurring when a person
clicked the login button twice, the enter key twice or both after entering
their credentials. We added some javascript to prevent the form
submission. It was likely lagging during the Duo preauthorization.
------------------------------
*James Gross* | Enterprise Application and CMS Developer (Enterprise Web
Services)
UNC Charlotte | Information Technology Services
9201 University City Blvd. | Charlotte, NC 28223
Phone: 704-687-0298 | Office: Kennedy 301-C39
jgross15 at uncc.edu | http://www.uncc.edu
------------------------------
If you are not the intended recipient of this transmission or a person
responsible for delivering it to the intended recipient, any disclosure,
copying, distribution, or other use of any of the information in this
transmission is strictly prohibited. If you have received this transmission
in error, please notify me immediately by reply e-mail or by telephone at
704-687-0298. Thank you.
On Mon, Nov 9, 2015 at 4:00 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 11/9/15, 2:57 PM, "James Gross" <JamesGross at uncc.edu> wrote:
>
>
>
> >Here is an example from the logs (scrubbed for user data). It actually
> looks like the entire process completes and then the user is returned
> either by the IdP or the SP immediately without the proper SAMLRequest.
>
> The audit log line happens only when the response is shipped back out, and
> the next step is accessing the SP, not the IdP. Getting a low level client
> trace is really the only option.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20151117/bfcf441e/attachment.html>
More information about the users
mailing list