IDP 2.3.6 Stops Sending SAML Responses.

[Cantor, Scott]

On 5/2/12 1:34 PM, "Montoya,Jose T" <jtmontoya at mdanderson.org> wrote:
>Well, no that's not what I was suggesting. But a log sync can be
>implemented that
>Does not require a file or a remote server, but just a client.

And any client can fail, putting you in the same position you're in now.
The reality is that a log appender must work, period. That's the contract.
A breach of the contract is a bug in the appender.

If the file appender responded to a file system filling up by hanging, I'd
say the same thing. I don't think it does though.

Note that there are plenty of tools for relaying log file content to
syslog. We use minion here, a Perl-based script. It also solves the async
problem.

> Some applications implement a client Which attaches to the service and
>displays the log. The logger would not depend on something capturing the
>information therefore causing the hang up. It would just happily log to
>this sync hoping someone would attach and view it. It would be more for
>debugging rather than for compliance reasons. Maybe this kind of logging
>option would have been able to indicate that there was a problem with
>sending responses due to logging issues.

And that's done by configuring exactly that sort of logging appender in
your system. It would be wrong to impact the IdP code with that
requirement when the logging layer already has a pluggable mechanism for
acomodating that exact need.

-- Scott