IdPv3 CAS Debugging

[Lucia Siochi]

Thanks for the suggestions. Also, I have filed the following RFE:
https://issues.shibboleth.net/jira/browse/IDP-952


------------------
Lucia Siochi
Senior Systems Architect, IT Services
Central Piedmont Community College
Central Campus, Citizens Bldg
704.330.6521

We value your feedback. How is our service at CPCC?


Message: 1
Date: Tue, 15 Mar 2016 13:35:39 +0000
From: "Cantor, Scott" <cantor.2 at osu.edu>
To: Shib Users <users at shibboleth.net>
Subject: RE: IdPv3 CAS Debugging
Message-ID:
        <9846A6064BD102419D06814DD0D78DE112876C53 at CIO-TNC-D2MBX02.osuad.osu.edu>

Content-Type: text/plain; charset="utf-8"

> Feel free to file a RFE issue for this if you'd like. I think I could
> work in approach #2 to apply just to CAS protocol views now that I think about it.
> Ideally the same logger that dumps SAML protocol messages would
> include CAS protocol messages as well.

We could just have the same property apply to both loggers, I think (which might be what you meant).

-- Scott



------------------------------

Message: 2
Date: Tue, 15 Mar 2016 13:53:14 +0000
From: Marvin Addison <marvin.addison at gmail.com>
To: Shib Users <users at shibboleth.net>
Subject: Re: IdPv3 CAS Debugging
Message-ID:
        <CACOs9MSA6hxvbHfOeU93MfqEt2XzavT_zRf94d5V4Kto+S0DCg at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

On Tue, Mar 15, 2016 at 9:35 AM Cantor, Scott <cantor.2 at osu.edu> wrote:

> We could just have the same property apply to both loggers, I think
> (which might be what you meant).
>

That's only part of the fix afaict. I'd need to implement the plumbing to make velocity write out the rendered template to a logger, which is what the gist outlines. The logger category would be derived from the property.

M <users-unsubscribe at shibboleth.net>


This e-mail, including any attachments, is intended only for the addressee's use and may contain confidential and proprietary information. If you are not the intended recipient, you are hereby notified that any retention, dissemination, reproduction, or use of the information contained in this e-mail is strictly prohibited. If you have received this e-mail by error, please delete it and immediately notify the sender. Thank you for your cooperation.