[TechNote] Disabling global security

Disabling global security

Problem(Abstract)

If you cannot access the administrative console due to security errors, you may need to disable global security. This technote describes how to disable global security when you cannot get to the administrative console.

Resolving the problem

You can disable security by modifying the security.xml file(s).

If you are running the based edition of IBM® WebSphere® Application Server only:
There is only one security.xml file to change if you are running the base Application Server alone.
The security.xml file is located under WSAS_install_root/profile/profile_name/config/cells/cellname. Always store a copy of the security.xml file in a temporary directory before making any changes.
To disable security:
Open the security.xml file and search for the very first occurrence of enabled="true". This is located inside the <security:> tag.
Change enabled="true" to enabled="false", then save the file.
You must restart the server for the change to take effect.

If you are running a Deployment Manager
There are two security.xml files you need to change:
WSAS_install_root/profiles/node_profile/config/cells/cellname/security.xml
WSAS_install_root/profiles/dmgr_profile/config/cells/cellname/security.xml
Always store a copy of the security.xml file in a temporary directory before making any changes.
Open each security.xml file and search for the very first occurrence of enabled="true". This is located inside the <security:> tag.
Change enabled="true" to enabled="false", then save the file.
You must restart the Deployment Manager, the nodegent and then the Application Servers, in that order.