When describing the Avaya Oceana Monitor, which cluster will have a monitoring snap-in installed that will create a web socket subscription service to feed statistics?
After the new implementation has been performed by the Avaya Business Partner, a customer is trying to login to their Agents Workspaces. While the agent is trying to login, the engineer finds the following error messages:
2018-04-19 06:04:45,386 [WebContainer : 4] AuthorizationService ERROR -- AuthorizationService-3.4.0.0.340003 -- Caught exception while authenticating with data source: HR-LAB
javax.naming.CommunicationException: 135.35.67.19:636 [Root exception is java.net.ConnectException: Connection timed out]at
com.avaya.zephyr.services.production.AuthorizationService.ldap.LdapDAOClientImpl.handleAuthenticationSystemException(LdapDAOClientImpl.java:116)
Which Avaya Oceana snap-in log file contains these log messages?
A customer is unable to login to Agent Workspaces, and the administrator finds the following error messages in the log files.
2018-04-19 06:04:45,386 [WebContainer : 4] AuthorizationService ERROR -- AuthorizationService-3.4.0.0.340003 -- Caught exception while authenticating with data source: HR-LAB
javax.naming.CommunicationException: 135.35.67.19:636 [Root exception is java.net.ConnectException: Connection timed out]at
com.avaya.zephyr.services.production.AuthorizationService.ldap.LdapDAOClientImpl.handleAuthenticationSystemException(LdapDAOClientImpl.java:116)
What is causing these error messages?
If not using Security Assertion Markup Language (SAML) authentication in the deployed solution which statement regarding the Avaya Oceana Agent/Supervisor Login is correct?
