SAML2StringEncoder Name for RelationalDatbase Attribute

[Peter Schober]

* David E. Newswanger <David_Newswanger at berea.edu> [2016-03-15 21:59]:
> I'm trying to configure shibboleth to pull attributes from a MySQL
> database. How do I figure out what the name is for the attribute
> encoder for a MySQL column name? LDAP attributes have an OID which
> is usually something along the lines of  2.5.4.4, which would
> translate to the following AttributeEncoder:
> 
> <resolver:AttributeEncoder xsi:type="enc:SAML2String"
> name="urn:oid:2.5.4.4" friendlyName="sn" encodeType="false" /> 
> 
> As far as I can tell (and I may be wrong), MySQL doesn't haven an
> OID for each attribute. What should I put in the name section for
> the AttributeEncoder element of some attribute that I get out of a
> MySQL table?

If you mean the OID is what decides what attribute to pull from LDAP,
that's not the case here. You reference LDAP attribute the same way as
ones provided from an RDBMS connector: Using their attribute or column
names.
In both LDAP and RDBMS you can also do additional mapping in the
connector (to rename the column while still in the data connector).

You pull those into an attribute definition using a dependency on the
data connector, plus the sourceAttributeID to identify the
attribute/column.
Once you have those in the attribute definition you can assign any
encoder you want to that, including something completely unrelated to
where it came from. That decides the on-the-wire representation of the
data structure, not more and not less.
-peter