Maximo EAM

 View Only

  • 1.  You cannot log in at this time. Contact the system administrator.

    Posted Wed July 22, 2020 10:36 PM
    I am working with a single server Maximo system that has WAS and DB2 on the same machine. This is a VM hosted in a cloud solution.
    When I installed it originally I set the maxadmin,mxintadm,and maxreg password to something I know and started learning maximo.Everything was kosher and working.
    I wanted to see if I can create a user called maxadmin@mycompanydomain.com and see if I can bring in AD synchronized accounts. For that I created a maxadmin@mycompanydomain.com in our AD and started following this article https://www.ibm.com/support/pages/maximo-and-ldap-configuration-start-finish I did all the steps to the WAS brought the users from AD and updated the 4 web.xml files and did the useAppServerSecuriy=1 
    I then rebuilt the new ear file and deployed it.
    Now when I logon to the application that I had bookmarked prior to this server/maximo/ui/ I get the You cannot log in at this time. Contact the system administrator.

    in the article it says something like this. I understood it as most users would leave BASIC at App Server on.Should I have commented that and left the commented parts on



    At this point since I cannot get into maximo I cannot do the VMSYNC job to bring in others but I would be happy to get into maximo with maxadmin
    I referred to this article
    https://community.ibm.com/community/user/iot/participate/blogs/blogviewer?BlogKey=4d046e5e-b9fa-44bf-8191-d331faa0d2e9

    that said to check if MAXADMIN in MAXUSER is active it is so is he in PERSON table

    this table has no rows as well select * from loginblock;

    The system.out.log records corn stuff so I know that maximo is running but I cannot seem to find the login failure it comes cryptic for second if I restart Websphere 

    the error URL changes to this HTTP://server/maximo/webclient/login/loginerror.jsp?group=system&key=NoLogin

    Some threads talk about a time variation then why was my maxadmin working before the change?

    Perhaps rookie mistakes but I have twice done the same exercise with the same outcome...










    ------------------------------
    Appu Nair
    ------------------------------


  • 2.  RE: You cannot log in at this time. Contact the system administrator.

    Posted Thu July 23, 2020 09:20 AM
    Ok this is what I get when the URL is submitted

    [7/23/20 12:52:45:620 UTC] 000058c3 ServletWrappe I com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: [MAXIMO] [/maximo] [/webclient/login/logout.jsp]: Initialization successful.
    [7/23/20 12:52:45:879 UTC] 000058c3 ServletWrappe I com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: [MAXIMO] [/maximo] [/webclient/login/loginerror.jsp]: Initialization successful.

    ------------------------------
    Appu Nair
    ------------------------------

    Original Message


  • 3.  RE: You cannot log in at this time. Contact the system administrator.

    Posted Tue August 11, 2020 09:22 AM
    I was able to continue with Synching LDAP users into our Maximo . In my configuration, I left the basic authentication commented out and started using the Form-Based authentication. With Basic enabled, I get prompt but not sure how to get it suppressed. Still what this does is allow a user in AD who has an ID in maximo to use its password. Is SSO a common practice in Maximo big users whereas you do not see a userid/password field but handled transparently by passing off Kerberos authentication?

    ------------------------------
    Appu Nair
    ------------------------------

    Original Message