possible 2.3.3 idp regression
James Bardin
jbardin at bu.edu
Tue Sep 27 14:53:35 BST 2011
I was updating my dev system to 2.3.3, and the config there threw the
error below. It turns out that edupersonTargetedID was being released twice, in
different AttributeFilterPolicy blocks.
ERROR [edu.internet2.middleware.shibboleth.common.profile.ProfileRequestDispatcherServlet:89]
- Error occurred while processing request
java.lang.IllegalArgumentException:
{urn:oasis:names:tc:SAML:2.0:assertion}NameID is already the child of
another XMLObject and may not be inserted in to this list
Just checking if I should file a bug, or if this is expected because
of the change in de-duping behavior. My only real problem is that it
was a hard error, and stopped the authentication flow altogether, but
it was easily fixed in the attribute filters.
Thanks,
-jim
--
James Bardin <jbardin at bu.edu>
Systems Engineer
Boston University IS&T
More information about the dev
mailing list