IDP 3 attribute-resolver.xml, unable to avoid XML warnings
rdw at steadingsoftware.com
Tue Apr 19 10:49:46 EDT 2016
> Thanks for the explanation. I also have an AttributeDefinition of type
> with about ten "Dependencies" and I removed the "sourceAttributeID" and it
> works just fine, no warnings at all. (I got a warning before I removed
> "sourceAttributeID".) Perhaps you could configure the "Mapped" type to
> the same as "Script" since they both allow multiple dependencies. If not,
> deal, now that I know that my config file is OK.
To be honest I'm not sure that the correct thing to do is to supress the
warn (or demote it to a debug). People haven’t been bitten in all the years
that this has been an issue and two people have independently tripped over
the new warning.
The difference between the scripted and mapped attribute definitions
explains the reason why you see no error. Scripted attributes do not have a
meaningful "sourceAttributeID" - they just have a bunch of dependencies,
mapped ones definitions require an attributeID; but is also suggests the
workaround (which you'll hate) - combine authService/isMemberOf and
isMemberOf/isMemberOf into one attribute in a script and then use that as
input to the mapping.
But I don't think that you should have to do this.
More information about the users