|Applies To||Affected Versions: 4.X; 3.6.X|
This kbase refers to older V3 nd V4 ACM versions. The latest ACM V5 and V6 product documentation for all server types, Jboss, WebSphere and WebLogic now include instructions on how to setup test authentication. This 'documented' set of instructions supercedes the information presented here.
The TestAuth will allow any user collected by the specified IDC to access the appliance using any password or a common global password.
The TestAuth is not to be used in production but for testing only.
1. Determine the ID of the IDC that will be used for the TestAuth, it can be any IDC that has already run and successfully collected users.
select ID, NAME from T_DATA_COLLECTORS;
2, Add the TestAuth configuration to the Aveksa database.
(Note: the SQL is all on one line and replace the "1" in red with the correct IDC for the environment from step #1)
INSERT INTO T_AUTH_CONFIGURATIONS
3. Configure the TestAuthProvider for the target application server.
For Tomcat (with Aveksa 3.X)
For jboss (with Aveksa 4.x)
For Weblogic (with Aveksa 4.1)
a. Edit or create a jaas.config file and place the following lines in it
b. Edit the setDomainEnv.sh (typically found in $WL_HOME/user_projects/domains/base_domain/bin
For Websphere (with Aveksa 4.1)
Refer to existing Aveksa WebSphere Installation documentation.
For Tomcat or Jboss
$ sudo service aveksa_agent stop 3.X only
$ sudo service aveksa_server start
$ sudo service aveksa_agent start 3.X only
5. Optional - Configure a 'common' password for all users:
a. Go to Admin/System Tab
b. Click on Edit
c. Add a Property "TestAuthProviderUserPassword" and desired password value
d. Hit Save
Users should now be able to log in with their standard User ID and any password of you configured a common password all users must now use that common password.
|Notes||You can configure multiple TestAuth providers for multiple IDCs the would then be called TestAuth TestAuth2 etc.|