Log in as a root user to Protected Resource 2.
# cd /opt/j2ee_agents/am_wl9_agent/agent_001/config
Make a backup of the file AMAgent.properties.
In the AMAgent.properties file, set the following properties:
com.sun.identity.agents.config.login.url[0] = https://LoadBalancer-4.example.com:9443/distAuth/UI/Login?realm=users |
Save the file.
Restart the Application Server.
Stop Application Server 2.
# cd /usr/local/bea/user_projects/domains/ProtectedResource-2/bin # ./stopManagedWebLogic.sh ApplicationServer-2 t3://localhost:7001
Stop the administration server.
#cd /usr/local/bea/user_projects/domains/ProtectedResource-2/bin ./stopWebLogic.sh
Start the administration server.
# nohup ./startWebLogic.sh & # tail -f nohup.out
Watch for startup errors.
Start Application Server 2.
# nohup ./startManageWebLogic.sh ApplicatoinServer-2 http://ProtectedResource-2.example.com:7001 & tail -f nohup.out
Verify that the agents are configured properly.
Go to the sample application URL:
http://ProtectedResource-2.example.com:1081/agentsample/index.html
In the left navigation bar, click “Invoke the Protected Servlet.”
You are redirected to the Distributed Authentication UI server URL https://loadbalancer-4.example.com:9443/distAuth/UI/login. The Access Manager login page is displayed.
Double-click the gold lock in the lower left corner of the browser.
In the Properties page, you see certificate for LoadBalancer–4.example.com.
Log in to the Access Manager console using the following information:
testuser1
password
You are redirected to the protected servlet of the Sample Application, and a success message is displayed. This indicates that authentication through the Distributed Authentication UI server was successful.