Hi, Vipin. oxTrust (Gluu's web UI) regenerates those files each time any SAML TR is created or updated, or when its service is restarted. It utilizes Apache Velocity templates stored in ` /opt/gluu/jetty/identity/conf/shibboleth3/idp/`. If you need to modify them (what we strongly recommend against, unless you are sure that must be done), you need to edit those templates, but in a such way that it won't ruin the general logic of it. This implies some knowledge of Velocity engine. Please note that free Community support doesn't cover such indepth subjects. Apache Velocity is a well-documented technology, in case you are not familiar with it yet.

Thanks for the details. Can we just have the config if possible for not updating the relying party.xml as we are trying to do the Shibboleth features directly on Gluu.

We don't have such option, it turns out. You may try to rename corresponding template(s) perhaps, may be oxTrust will just ignore its absence gracefully.

..Other option: you could try to simply copy the content of the final configuration file into file of corresponding template. Thus instead of generating it each time oxTrust will just copy it as it is. Then you'll be updating that template file whenever you need to change something. This way you won't need to deal with Velocity and will be able to work with clean Shibboleth conf file(s). A little clumsy, but should work. You may want to do a backup of template dir first.