Attributes retrieved from database are not getting resolved

[Achugatla, Vijay Kumar (ELS-CON)]

Scott,

Interestingly that issue got fixed by changing the column names to upper case

before
        <dc:Column columnName="edupersonentitlement" attributeID="eduPersonEntitlement" />
        <dc:Column columnName="edupersontargetedid" attributeID="eduPersonTargetedID" />

After
        <dc:Column columnName="EDUPERSONENTITLEMENT" attributeID="eduPersonEntitlement" />
        <dc:Column columnName="EDUPERSONTARGETEDID" attributeID="eduPersonTargetedID" />

I am not sure why its expecting the upper case column names. Let me know if there is any technical reason for that 

Thanks,
Vijay


-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Chad La Joie
Sent: Tuesday, April 03, 2012 7:42 PM
To: Shib Users
Subject: Re: Attributes retrieved from database are not getting resolved

Doesn't TOAD use the thick client?

On Tue, Apr 3, 2012 at 18:44, Achugatla, Vijay Kumar (ELS-CON) <vijay.achugatla at lexisnexis.com> wrote:
> Scott,
>
> I ran the same query using a oracle client (TOAD) and I got the 
> expected results back. Is there a way I can see the result of the 
> query in the logs? I tried setting the log level to TRACE but it did 
> not log the results Any suggestions would be appreciated
>
> Thanks,
> Vijay
>
> -----Original Message-----
> From: users-bounces at shibboleth.net 
> [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
> Sent: Friday, March 30, 2012 12:46 PM
> To: Shib Users
> Subject: RE: Attributes retrieved from database are not getting 
> resolved
>
>> Is there anything wrong with my configuration. I am not understanding 
>> why the attributes are not getting resolved
>
> I would imagine your database has no such data in it.
>
>> Issue 2: AttributeDecoder formatter is stripping off a part of 
>> eduPersonTargetedID value
>
> That value is improper, that is not a syntactically correct expression. eduPersonTargetedID isn't a scoped attribute, it's NameID-valued. Given the rest, you may be doing that intentionally to test behavior when dealing with broken IdPs.
>
> You are using the compatibilty decoder designed to help migrate applications dealing with IdPs providing invalid values that are scoped. You are then telling it to serialize the value using only the "Name" component of the resulting NameID. That's your choice, the formatter can embed the different pieces however you want it to.
>
> And that's your change. That's not a default configuration, so you had to have chosen to change it.
>
>> Please let me know if you have any suggestions on how to handle these 
>> two issues?
>
> Well, for the second issue, read the documentation on the decoder settings you're using. If you don't understand it, tell me what it is you don't understand so I can improve it.
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to 
> users-unsubscribe at shibboleth.net
> --
> To unsubscribe from this list send an email to 
> users-unsubscribe at shibboleth.net



--
Chad La Joie
www.itumi.biz
trusted identities, delivered
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net