RelationalDatabaseConnector with InputDataConnector
cantor.2 at osu.edu
Thu Jul 30 18:59:28 UTC 2020
On 7/30/20, 2:46 PM, "users on behalf of Joseph Fischetti" <users-bounces at shibboleth.net on behalf of Joseph.Fischetti at marist.edu> wrote:
> Thank you Scott. I thought it was likely that I was listing them incorrectly (I didn't think it made sense that they would
> be available with InputAttributeDefinition, and not with InputDataConnector).
Well, you may have rationally followed the completely incorrect example in the documentation, which is fixed (I made a rare change to the V3 docs as well).
> Is one method preferred over the other?
You're just creating more XML to maintain and more work for the system defining an AttributeDefinition if there's a data connector result that already has the values and format you need. That's always been true in this kind of case, it's just more true now because you can export resolved attributes out of data connectors and don't need AttributeEncoders anymore.
More information about the users