Agent configuration for Liberty-based federation

Question

Hi all,
I am using AccessManager 7.1, and I was wondering to test the liberty-based federation authentication. I configured my authentication domain in the AM server, but then I had to configure the agent.
In the tutorial there's information about how to configure it:
Point the com.sun.am.policy.loginURL property in the AMAgent.properties file to the pre-login service URL running on Access Manager.
but the j2ee agent (2.2 for tomcat) I installed has no property like that. I found something similar: the com.sun.identity.agents.config.login properties list, but I'm not sure I can use this instead of the loginURL property. Moreover, there are some webservices related properties like com.sun.identity.agents.config.webservice.enabled. The default value for the webservice.enabled is false, I suppose it must be changed to true, but what about the endpoints list? The authenticator property must point to an implementation class, so it is not what I need.
How can I configure the agent to protect web services?
Thank you.

Answer 1

Hello Davinder,
Even though the parameter is there, it must be accessible for checking.
In order to get the profile value of the managed system we use a webservice handled by sapstartsrv on port 56013. It seems that this port is not listening: sapstartsrv is probably stopped.
You can see it here:
"!! Exception : Service call exception; nested exception is:
java.net.ConnectException: Connection
refused(cause=java.net.ConnectException Connection refused)"
Would you please check that sapstartsrv is up and running, then check that port 56013 is listening and then please restart the setup.
Note that your port number might be different.
Additional information:
As mentioned in the Note 936273,
"The start service is integrated into the Unix operating system using the
"sapinit" script as well as entries for each instance in
"/usr/sap/sapservices" (see Note 823941 (UNIX) or Note 893215(IBM i)).
So please check the Note 823941 and 936273 to set up the autostart of the sapstartsrv. Then restart your system and then you can check whether  sapstartsrv is started by
- 'ps -ef   grep sapstartsrv' command.
- '/sbin/init.d/sapinit status' command.
Best regards,
Guilherme