Scribd
Upload
17 views2 pages

IBM - Disabling global security WAS

Uploaded by

Hermes
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
17 views2 pages

IBM - Disabling global security WAS

Uploaded by

Hermes
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

IBM - Disabling global security http://www-01.ibm.com/support/docview.wss?rs=180&context=SSEQT...

Document information
Disabling global security Product categories:
Software

Technote (troubleshooting) Application Servers


Distributed
Problem(Abstract) Application & Web
If you cannot access the administrative console due to security errors, you Servers
may need to disable global security. This technote describes how to WebSphere
disable global security when you cannot get to the administrative console. Application Server
Security
Resolving the problem
You can disable security by modifying the security.xml file(s). Operating system(s):
AIX, HP-UX, Linux,
If you are running the based edition of IBM® WebSphere® Solaris, Windows
Application Server only: Software version:
5.1, 6.0.2, 6.1, 7.0
There is only one security.xml file to change if you are running the base
Application Server alone. Software edition:
Edition Independent
The security.xml file is located under WSAS_install_root/AppServer/config
/cells/cellname. Always store a copy of the security.xml file in a temporary Reference #:
directory before making any changes. 1105430
IBM Group:
To disable security:
Software Group
Open the security.xml file and search for the very first occurrence of Modified date:
enabled="true". This is located inside the <security:> tag. 2005-05-20
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/AppServer/config/cells/cellname/security.xml

WSAS_install_root/DeploymentManager/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.

Cross Reference information


Segment Product Component Platform Version Edition

1 de 2 22/04/2010 04:31 p.m.


IBM - Disabling global security http://www-01.ibm.com/support/docview.wss?rs=180&context=SSEQT...

Runtimes
Application
for Java Java SDK
Servers
Technology

Copyright and trademark information

IBM, the IBM logo and ibm.com are trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide. Other product
and service names might be trademarks of IBM or other companies. A
current list of IBM trademarks is available on the Web at "Copyright and
trademark information" at www.ibm.com/legal/copytrade.shtml.

2 de 2 22/04/2010 04:31 p.m.

You might also like