 |
 |
> LexisNexis have said that the problem lies with us It should be relatively simple to prove this. Turn on SAML logging (look for PROTOCOL_MESSAGE in logging.xml) and the next time someone sees this take a look in the log to see what was issued. Two options: either the targetted ID was issued in which case you can point this to LexisNexis, or you didn't issue it in which case the logging trail above may help. If it doesn't you may want to turn on debug logging for the attribute resolver (or everything if you don't mind the log bloat) and see what's up. Rod From: Discussion list for Shibboleth developments [mailto:[log in to unmask]] On Behalf Of Elaine Blair Sent: 21 January 2011 13:38 To: [log in to unmask] Subject: Is anyone having problems with LexisNexis? We have had intermittent problems with users trying to authenticate using Shibboleth to LexisNexis over the past week. Some of our users are getting the error message: - ShortErrorMessage = The eduPersonTargetedID is null. This is not allowed. LexisNexis have said that the problem lies with us. We are only seeing this problem with LexisNexis and wonder if anyone else is having a problem? Thanks Elaine --- Elaine Blair Faculty Librarian Science University of Strathclyde Andersonian Library Curran Building 101 St. James Road Glasgow G4 0NS Tel: 0141 548 4629 E-mail: [log in to unmask] The University of Strathclyde is a charitable body, registered in Scotland, number SC015263.