Enable security

We can use scripting to enable or disable application security, global security, administrative security based on the LocalOS registry, and authentication mechanisms.

Before starting this task, wsadmin.sh must be running. See the Starting the wsadmin scripting client article for more information.

The default profile sets up procedures so that we can enable and disable administrative security based on LocalOS registry.

• Use the isAppEnabled command to determine if application security is enabled or disabled:

  • Jacl:

    $AdminTask isAppSecurityEnabled {}

  • Jython:

    AdminTask.isAppSecurityEnabled()

  This command returns a value of true if appEnabled is set to true. Otherwise, returns a value of false.

• Use the isGlobalSecurityEnabled command to determine if administrative security is enabled or disabled:

  • Jacl:

    $AdminTask isGlobalSecurityEnabled{}

  • Jython:

    AdminTask.isGlobalSecurityEnabled()

  Returns a value of true if enabled is set to true. Otherwise, returns a value of false.

• Use the setGlobalSecurity command to set administrative security based on the passed in value:

  • Jacl:

    $AdminTask setGlobalSecurity {-enabled true}

  • 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.

• Use the help command to find out the arguments that provide with this call:

  • Jacl:

    securityon help

    Example output:

    Syntax: securityon user password

  • Jython:

    securityon()

    Example output:

    Syntax: securityon(user, password)

• Enable administrative security based on the LocalOS registry:

  • Jacl:

    securityon user1 password1

  • Jython:

    securityon('user1', 'password1')

• Disable administrative security based on the LocalOS registry:

  • Jacl:

    securityoff

  • Jython:

    securityoff()

• Enable and disable LTPA and Kerberos authentication.

  Use the setActiveAuthMechanism command to set Kerberos as the authentication mechanism in the security configuration:

  AdminTask.setActiveAuthMechanism('-authMechanismType KRB5')

  Use the setActiveAuthMechanism command to set LTPA as the authentication mechanism in the security configuration:

  AdminTask.setActiveAuthMechanism('-authMechanismType LTPA')

  Additionally, there are sample scripts located in the <WAS_ROOT>/bin directory on how to enable and disable LTPA authentication. The scripts are:

  • LTPA_LDAPSecurityProcs.py (python script)

  • LTPA_LDAPSecurityProcs.jacl (jacl script)

  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.

Related tasks

Configure security

Enable security for the realm

Get started with wsadmin scripting

Start the wsadmin scripting client

Kerberos authentication commands