IdP can't populate values from SQL

Matthew Holmes Matt.Holmes at nottingham.ac.uk
Wed Jun 27 12:40:01 BST 2012


Hi,

I wondered if it was a filter issue, but everything looked fine. As a last resort, I just tried commenting out the column mapping section in the attribute-resolver and now it works. I previously used this configuration in 1.3 and assumed it would continue to work, but it appears having a column mapping will conflict with the sourceID attribute in the AttributeDefinition tags.

For reference, here is the code I'm referring to as 'column mapping', it follows the <QueryTemplate ... /> section: 
<Column columnName="UniversityCardNumber" attributeID="https://www.nottingham.ac.uk/shibboleth/attributes/UniversityCardNumber" /> 

Matthew Holmes
Analyst Programmer, Business Systems Development Team
Information Services, The University of Nottingham


-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Chad La Joie
Sent: 27 June 2012 12:10
To: Shib Users
Subject: Re: IdP can't populate values from SQL

You'll need to check the logs.  If the IdP isn't sending the attributes, which the logs will tell you, then it's probably a filter issue (which the logs would also tell you).  If it is sending the attributes then it's an SP issue.

On 6/27/12 7:00 AM, Matthew Holmes wrote:
> Hi,
> 
>  
> 
> For a number of days now, I've been trying to configure our IdP 
> (v2.1.5) to retrieve custom attributes such as UniversityCardNumber 
> from a SQL Server 2005 database. I receive no errors in the 
> idp-process.log which I've got cranked up to DEBUG, and SQL Profiler 
> shows valid SQL queries are running against the database from the IdP. 
> However, the IdP does not appear to be able to set values for the 
> attributes. It keeps removing the attribute from the reply to the SP as "it contains no values".
> 
>  
> 
> I have swapped JDBC drivers and tried both Container Managed and 
> Application Managed connections; neither has made any difference. Even 
> replacing the SQL query with SELECT '1234567' AS UniversityCard has 
> made no difference. I have verified that the queries running under the 
> IdP's SQL credentials do produce results, so I'm quite puzzled by this behaviour.
> 
>  
> 
> I realise our IdP is a few versions behind, but wondered if anyone 
> else had encountered these problems, or knew if this is a bug resolved 
> in later versions of the IdP?
> 
>  
> 
> Thanks,
> 
>  
> 
> *Matthew Holmes*
> 
> *Analyst Programmer, Business Systems Development Team*
> 
> Information Services, The University of Nottingham
> 
>  
> 
> 
> This message and any attachment are intended solely for the addressee 
> and may contain confidential information. If you have received this 
> message in error, please send it back to me, and immediately delete it.
> Please do not use, copy or disclose the information contained in this 
> message or in any attachment. Any views or opinions expressed by the 
> author of this email do not necessarily reflect the views of the 
> University of Nottingham.
> 
> This message has been checked for viruses but the contents of an 
> attachment may still contain software viruses which could damage your 
> computer system: you are advised to perform your own checks. Email 
> communications with the University of Nottingham may be monitored as 
> permitted by UK legislation.
> 
> 
> 
> --
> 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


More information about the users mailing list