i too am having a similar issue, staying posted for an answer!

Hi, Ben, Joe. Please check oxTrust's logs at `/opt/gluu/jetty/identity/logs/oxtrust.log` for any errors related to this operation.

I assume you'll see some schema conflict errors there. Here is excerpt from our internal wiki page on adding support for ePSA: - Stop solserver - Modify `eduperson.schema`: - Location: `/opt/symas/etc/openldap/schema` - Add: attributetype ( 1.3.6.1.4.1.5923.1.1.1.9 NAME 'eduPersonScopedAffiliation' DESC 'eduPerson per Internet2 and EDUCAUSE' EQUALITY caseIgnoreMatch SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' SINGLE-VALUE ) - Add `eduPersonScopedAffiliation` in OC: objectclass ( 1.3.6.1.4.1.5923.1.1.2 NAME 'eduPerson' AUXILIARY MAY ( eduPersonAffiliation $ eduPersonNickname $ eduPersonOrgDN $ eduPersonOrgUnitDN $ eduPersonPrimaryAffiliation $ eduPersonPrincipalName $ eduPersonEntitlement $ eduPersonPrimaryOrgUnitDN $ eduPersonScopedAffiliation ) ) - Test configuration with command: `# /opt/symas/bin/slaptest -f /opt/symas/etc/openldap/slapd.conf` - Start openldap: `# service solserver start`

That got it for me. Is there any particular reason that an Attribute would show up in the GUI but not actually be in the schema?

Glad to hear it helped, I'll be closing the ticket then. >Is there any particular reason that an Attribute would show up in the GUI but not actually be in the schema? As Gluu decided to switch from OpenDJ to OpenLDAP in 3.0, there still may be minor schema issues like this one. It'll mostly be sorted out in the upcoming 3.0.2 release.