By: Thomas Maerz user 19 Feb 2018 at 6:02 a.m. CST

3 Responses
Thomas Maerz gravatar
I see that in this version we can now create custom NameID from the GUI. The GUI seems to inject the NameID directly into the attribute-resolver.xml file without being overwritten by the velocity templates, and it looks like it's stored in LDAP at ou=oxtrust,ou=configuration,inum=@!7F21.58E1.09AF.1CA4!0002!93F8.1626,ou=appliances,o=gluu in the entry oxTrustConfAttributeResolver. My question is, once I enter something here, how do I delete it? Also, it seems like you can only enter one thing here. If I change what is in the field and register it again, it just changes the existing nameID, but still no way to erase/delete it. Is this expected behavior, or am I misunderstanding/missing something? Thanks, Thomas

By Mohib Zico Account Admin 19 Feb 2018 at 7:07 a.m. CST

Mohib Zico gravatar
This is not expected behavior. I think we should create an enhancement issue in [oxShibboleth](https://github.com/GluuFederation/oxShibboleth). For now, I would go with [manual setup](https://gluu.org/docs/ce/3.1.2/admin-guide/saml/#manual-configuration)

By Thomas Maerz user 23 Feb 2018 at 5:37 p.m. CST

Thomas Maerz gravatar
A note to anyone who reads this in the future: Connecting directly the LDAP server and deleting the field contents of oxTrustConfAttributeResolver is **NOT** a good idea. It will cause oxTrust to fail to parse the config on startup and you'll be greeted with an HTTP 503 - Service unavailable when you try to log in to the webui. At least -- The way I attempted to remove it is not a good idea. There may be some better surgical way to do this, I'm just not aware of it. If you do end up doing it, the only way I've found to undo it is to bring back a backup or VM snapshot of a known good configuration.

By Sahil Arora user 23 Feb 2018 at 6:17 p.m. CST

Sahil Arora gravatar
Hi Thomas, Thanks for the additional information. I have raised the [this ](https://github.com/GluuFederation/oxShibboleth/issues/39)enhancement request.