Anyone has come across this issue?
2/10/17 11:11:15.231 AM EST [WARN] [btpool1-1] [Manager] Authentication failed for user zz.vahn.ca.admin: Error authenticating user zz.vahn.ca.admin in realm EEM: com.wily.introscope.spec.server.beans.usermgmt.UserMgmtException: EEM failed to attach to EEM server
We just stood up a new EEM in our Dev Env and imported the "APM.xml" from our Prod EEM to Dev EEM. The output of 'safex' was successful. I pointed the Dev MoM to Dev EEM and restart it. Then I get the above message in MoM's log and now I am not able to access APM via the browser (WebView).
I tried using Wkst and was NOT successful either.
Thanks in advance for all your help.
These KBs (particularly the first) may help
Please let us know if they helped with the issue
Do I need to unregister from the prod EEM first and then register it with the Dev EEM?
It would be worth trying the registering/deregistering EEM as you describe. The KB also talks about hostname/IP address/hostname/ports configuration as a possible issue
SergioMorales Lynn_Williams any suggestions on this?
Per your first link, looks like my realms.xml is fine
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><realms xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="0.1" xsi:noNamespaceSchemaLocation="realms0.1.xsd"> <realm descriptor="EEM Realm" id="EEM" active="true"> <property name="username"> <value>EiamAdmin</value> </property> <property name="host"> <value>10.xx.xx.xx</value> </property> <property name="appname"> <value>APM</value> </property> <property name="plainTextPasswords"> <value>false</value> </property> <property name="enableAuthorization"> <value>true</value> </property> <property name="password"> <value>*********************</value> </property> </realm></realms>
Per the first KB Hal posted, have you tried restarting the MOM with plainTextPasswords set to true and the EiamAdmin password in plain text?
Yeah, already did that last week but as per my update below, I need to take care of the firewall rule and I think that will solve the issue.
We have not heard anything back from you so marking as answered. However, we want to hear from you on what you found looking at hostname/IP address/hostname/ports configuration as a possible issue and what happened after registering/deregistering EEMs. We will continue to assist as needed . Although this may soon be done through a case.
Sorry for not replying back sooner. I had completely forgotten that (internally) I need to submit a firewall request to our network guys to open up port (5250) comm between MoM and EEM via HTTPS
I have submitted the requested this morning and they will work on it tomorrow even as their standard change request.
I will update this post once I've checked everything on MoM side and EEM to ensure everything is working (as it should).
Thanks Manish. Please let us know either way after the firewall rule is deployed