Scripted Attribute - Javascript not logged?

[Ernie Kinsey]

Greg,

I would bet you’re right on that, thanks – I’m using a proto-production instance that does NOT log at that level.  I appreciate the tip.

Scott,

You’re right, my mistake – I saw that as soon as I got my copy and was thinking that was going to be a problem.

Ernie.

From: Greg Haverkamp <gahaverkamp at lbl.gov>
Reply-To: Shib Users <users at shibboleth.net>
Date: Tuesday, February 27, 2018 at 3:53 PM
To: Shib Users <users at shibboleth.net>
Subject: Re: [EXTERNAL] Re: Metagen/megagen.sh

On Tue, Feb 27, 2018 at 11:29 AM, Ernie Kinsey <Ernie.Kinsey at cpcc.edu<mailto:Ernie.Kinsey at cpcc.edu>> wrote:
All I’m looking for is to see the logging message ("Here we are, doing stuff ...") show up in my idp-process log, but – nothing.  I’m sure this is something fundamentally silly, but since the value itself is being properly fetched from the database – at least as far as what “aacli.sh” is telling me – I’m at a loss to understand why the script isn’t logging anything.  Any and all assistance would be much appreciated.

Are you logging net.shibboleth.idp.attribute.resolver at DEBUG?

Greg

________________________________

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.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <http://shibboleth.net/pipermail/users/attachments/20180227/9e75c793/attachment.txt>