You can use scripting to enable or disable administrative security. Before starting this task, the wsadmin tool must be running. See the Starting the wsadmin scripting client article for more information.
The default profile sets up procedures so that you can enable and disable administrative security based on LocalOS registry.
Using Jacl:
$AdminTask isAppSecurityEnabled {}
Using Jython:
AdminTask.isAppSecurityEnabled()
This command returns a value of true if appEnabled is set to true. Otherwise, returns a value of false.
Using Jacl:
$AdminTask isGlobalSecurityEnabled{}
Using Jython:
AdminTask.isGlobalSecurityEnabled()
Returns a value of true if enabled is set to true. Otherwise, returns a value of false.
Using Jacl:
$AdminTask setGlobalSecurity {-enabled true}
Using Jython:
AdminTask.setGlobalSecurity ('[-enabled true]')
Returns a value of true if the enabled field in the WCCM security model is successfully updated. Otherwise, returns a value of false.
Using Jacl:
securityon helpExample output:
Syntax: securityon user password
securityon()Example output:
Syntax: securityon(user, password)
Using Jacl:
securityon user1 password1
securityon('user1', 'password1')
Using Jacl:
securityoff
securityoff()
Enabling and disabling LTPA authentication There are sample scripts located in the <WAS_ROOT>/bin directory on how to enable and disable LTPA authentication. The scripts are:
Note: The scripts hard code the type of LDAP server and base distinguished name (baseDN). The LDAP server type is hardcoded as IBM_DIRECTORY_SERVER and the baseDN is hardcoded as o=ibm,cn=us.