So I ended up opening a ticket with my support Vendor - Below is the non-solution that I got. I guess we will call it an "undocumented Enhancement"....
"Here is the scope. Users that are authenticated via ASSO will have "authString" associated with their login. With this "authString" ASSO plug-in will validate the user with ASSO server. For user's don't have "authString" it will print out the message saying "authString" is null and External authentication is failed. but the applications are already authenticated with AR system and they continue to work. ASSO plug-in opens a connection to ASSO server to validate the login. Once validation is done connections will be closed by underlying JVM/TCPIP layers. If "authString" is null it won't even open a connection. None of these messages should cause any user login failures. If a user login is failed, then there could be another reason and at that time logs might give another reason (like some connectivity failure...) As the Users are able to login successfully the reported error in arjavaplugin can be ignored as ASSO appears to be working fine. One good practice is to make backups of these logs and clear them once a while. I will go ahead and close this request. Nothing can be done to remove/resolve the error and warning msg in the arjavaplugin.log. " _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
