IDP 2.3.6 Stops Sending SAML Responses.

[Cantor, Scott]

On 5/2/12 12:51 PM, "Montoya,Jose T" <jtmontoya at mdanderson.org> wrote:
>
>I would like for this issue to be considered a bug for the following
>reasons:

It is a bug, but the bug is with logback, not the IdP. I also don't think
it's good practice to remote syslog. I thought the usual idea was local
syslog, with syslog itself configured to relay the events, which takes
care of the async requirement. If not, then I'd say syslog is not
appropriate here. (Which in fact I think it's not, but that's a different
argument, and is subjective.)

>1. The IDP did not provide an obviously visible indicator that there was
>a logging problem.

If logging hangs, it seems to be impossible to provide such an indicator.
Are you suggesting logging the fact that it's about to log? I hope not.

>2. I'm not sure how strict the logging requirement is, but is it so
>strict that a failure to log a response should stop the idp from working?

I don't think logging justifies spinning up a thread to do the work, no.
Not everything can be implemented asynchronously. So yes, what happened is
what I would expect would happen (speaking as a deployer).

-- Scott