I suppose I found a bug while trying to generate Shibboleth SP config-files using the Gluu GUI. This is an excerpt of the resulting attribute-map.xml file, which contains faulty exported attribute definitions: <Attribute name="urn:oid:$attrParams.attributeOids.get($attribute.name)" id="uid"/> <Attribute name="urn:oid:$attrParams.attributeOids.get($attribute.name)" id="mail"/> <Attribute name="urn:oid:$attrParams.attributeOids.get($attribute.name)" id="displayName"/> <Attribute name="urn:oid:$attrParams.attributeOids.get($attribute.name)" id="givenName"/> <Attribute name="urn:oid:$attrParams.attributeOids.get($attribute.name)" id="sn"/> <Attribute name="urn:oid:$attrParams.attributeOids.get($attribute.name)" id="memberOf"/> As you can see the export worked, sort of. The list corresponds exactly to the user attributes I selected to be released, but the strings seem like variables were not expanded before writing to the output file. It should read something like this <Attribute name="urn:oid:urn:oid:0.9.2342.19200300.100.1.1" id="uid"/> etc. Steps to reproduce: I created a new trust relationship to a Shibboleth SP (new, house internal testing SP Apache + Moodle). Specified public cert, selected "Generate" method, entered URL, configured relying party, added attributes to be released, clicked "Update". After success message, I downloaded "Shibboleth 3 configuration files" ZIP file. The Gluu GUI does give the correct OID strings when I mouse-over the attributes.