powered by Jive Software

Openfire.xml <sasl> configuration is overwritten at Startup

I have been running Openfire 3.6.3 with Spark 2.5.8 in my production environement for about a year now and I have recently been asked to implement SSO.

I have completed all of the steps required to configure and use SSO and have been successful intermitantly connecting the test clients with SSO. What I have found is that when the Openfire Server is restarted the configuration is being overwritten. I am not sure if this is due to my SSO implementation or if this is normal startup behavior. My setup is as follows:

Server

Openfire 3.6.3

Windows Server 2003 R2 SP2
Active Directory Integration

Clients

Windows XP SP2

After stopping the openfire service I am adding the following to the openfire.xml

GSSAPI CORPORATEDOMAIN.COM true C:/Program Files/Openfire/conf/gss.conf false

After adding the SSO config I save and start the Openfire Service

After the service loads and I verify that I can access the admin console I attempt to connect my clients via SSO. The client login fails and when I look at the Openfire.xml the file has been modified as follows:

CORPORATEDOMAIN.COM

Can someone provide me with some insight as to what may be causing this?

Per an earlier thread, most of the SSO config gets sucked into the DB at startup, which is why you don’t see it in the XML file anymore. This is normal.