List of Contributions

Shanmugarajan M

This individual is no longer active. Application functionality related to this individual is limited.

Contact Details

My Content

1 to 8 of 8 total

RE: Do Node Agent in WAS restart itself at any situation?

Posted By Shanmugarajan M Wed March 27, 2019 08:18 AM
Found In Egroup: WebSphere Application Server & Liberty \ view thread
Hi Hermann I got to know that DMGR was restarted and Nodeagent was not restarted. and We got the info that node agent was started manually as it was down but not killed manually by anyone (got confirmation from AIX syslog).(sorry for the confusion). The ambiguity here is ,will it cause node ...

Do Node Agent in WAS restart itself at any situation?

Posted By Shanmugarajan M Tue March 26, 2019 03:18 AM
Found In Egroup: WebSphere Application Server & Liberty \ view thread
In WAS 7.0.0.37 - Node agent's SystemOut.log has traces for Node agent start but startNode.sh was not executed at that time., and before we could identify that Node agent cannot able to communicate with DMGR for more than 21 hours. At 15.33 CET ADMS0015E: The synchronization request cannot be completed ...

RE: max-concurrent-web-session policy not enforced

Posted By Shanmugarajan M Fri March 22, 2019 03:24 AM
Found In Egroup: IBM Security Verify \ view thread
Yes correct, our issue is we 're not getting the concurrent web session attribute for users that are coming via TFIM. It seems TFIM is using the ISAM Authorization Server and builds its registry attributes but not credential policy attributes. Do we have to add anything like the given below stanza ...

RE: max-concurrent-web-session policy not enforced

Posted By Shanmugarajan M Thu March 21, 2019 10:31 AM
Found In Egroup: IBM Security Verify \ view thread
In the RPX conf file, the stanza you have given is available . at the same time I have added this to ivacld.conf (authorization server;s conf). is there any way to add this (MAX_CONCURRENT_WEB_SESSIONS) as an attribute to the TFIM junction object like below , will it work? object modify /We ...

RE: max-concurrent-web-session policy not enforced

Posted By Shanmugarajan M Thu March 21, 2019 09:19 AM
Found In Egroup: IBM Security Verify \ view thread
And we are experiencing the following lines repeatedly in RPX log 87 2019-03-19-18:44:41.806+01:00I----- 0x38B9A426 webseald ERROR wns session WSRemoteCache.cpp 2924 0x7fca32df8700 -- DPWNS1062E An attempt to update a session failed with error code 0x38a0a13e. 88 2019-03-19-18:46:05.270+01:00I----- ...

RE: max-concurrent-web-session policy not enforced

Posted By Shanmugarajan M Thu March 21, 2019 08:32 AM
Found In Egroup: IBM Security Verify \ view thread
Hi Jon The profile name I can see in the RPX node's PoC is "Access Manager Username and extended attributes". In the authz server i have added the below stanza so that we would get the max sessions value to webseal but that didnt help [credential-policy-attributes] AZN_POLICY_M ...

RE: max-concurrent-web-session policy not enforced

Posted By Shanmugarajan M Thu March 21, 2019 06:46 AM
Found In Egroup: IBM Security Verify \ view thread
Can you please tell me , how to add that attribute ?(tagvalue_max_concurrent_web_sessions) ------------------------------ Shanmugarajan M ------------------------------

max-concurrent-web-session policy not enforced

Posted By Shanmugarajan M Tue March 19, 2019 09:24 AM
Found In Egroup: IBM Security Verify \ view thread
We have the distribution session deployed and enabled on reverse proxy nodes dsess-enabled = yes enforce-max-sessions-policy = yes prompt-for-displacement = yes dsess-cluster-name = dsess [dsess-cluster] server = 9,http://127.0.0.1:2035/DSess/services/DSess but reverse proxy ...