Set security with scripting


Configure security with scripting and wsadmin.

Before starting this task, wsadmin must be running. Read about Start wsadmin article for more information.

If we enable security for an appserver cell, supply authentication information to communicate with servers. The sas.client.props and the soap.client.props files are located in the following properties directory for each appserver profile:

 


Enable and disable security using scripting
Enable and disable Java 2 security using scripting
Set multiple security domains using scripting
Set the JACC provider for TAM using the wsadmin utility
Secure communications using wsadmin
Enable authentication in the file transfer service using scripting
Propagating security policy of installed applications to a JACC provider using wsadmin scripting
Set custom adapters for federated repositories using wsadmin
Disable embedded TAM client using wsadmin
Set security auditing using scripting
SSLMigrationCommands
IdMgrConfig
IdMgrRepositoryConfig
IdMgrRealmConfig
WIMManagementCommands
DescriptivePropCommands
ManagementScopeCommands
AuthorizationGroupCommands
ChannelFrameworkManagement
SpnegoTAICommands group for AdminTask (deprecated)
The Kerberos configuration file
SPNEGO Web authentication configuration commands
SPNEGO Web authentication filter commands
Kerberos authentication commands
LTPA_LDAPSecurityOn and LTPA_LDAPSecurityOff command usage

 

Related tasks


Use scripting (wsadmin)
Getting started with scripting

 

Related