MxLoader

 View Only

  • 1.  Can't get MXLoader to work with LDAP

    Posted 10-10-2022 11:25
    MXloader works beautifully for us in our test environments which use native maximo security.  Our production environment we have LDAP enabled and I can't get past this issue.

    Maximo 7.6.1.3

    Service: REST
    Authentication: LDAP

    Click test connection receive "Unexpected char in ParseObject"

    Upon reviewing the log:   
    https://<SERVER>/maximo/oslc/whoami?lean=1  the response returned is the html for the maximo login page.  This is because we have our maximo/applications/maximo/maximouiweb/webmodule/WEB-INF/web.xml   file configured for FORM based security

    <login-config>
    <auth-method>FORM</auth-method>
    <realm-name>MAXIMO Web Application Realm</realm-name>
    <form-login-config>
    <form-login-page>/webclient/login/login.jsp?appservauth=true</form-login-page>
    <form-error-page>/webclient/login/loginerror.jsp</form-error-page>
    </form-login-config>
    </login-config>


    <security-role>
    <description>MAXIMO Application Users</description>
    <role-name>maximouser</role-name>
    </security-role>

    <env-entry>
    <description>Indicates whether to use Application Server security or not</description>
    <env-entry-name>useAppServerSecurity</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>1</env-entry-value>
    </env-entry>


    If I manually type that address in a browser and then login it returns the JSON the spreadsheet is looking for.
    What am I missing here?

    ------------------------------
    Eric Burkland
    San Diego County Water Authority
    ------------------------------


  • 2.  RE: Can't get MXLoader to work with LDAP

    Posted 10-11-2022 12:02
    Edited by Matt McGuire 10-11-2022 12:02
    Hi Eric,

    You have a few options:

    1. Change Service/Authentication to OS/LDAP
    2. Change Service/Authentication to REST/API

    Option 1 you can use your LDAP username/password. Option 2 you can create an API key in the Administration Work Center. You then use the API key as the password on the config sheet (in this option you do not add a username).

    Please let me know if that doesn't resolve the issue.

    Thanks,

    ------------------------------
    Matt McGuire
    Aquitas Solutions
    https://www.aquitas-solutions.com/
    ------------------------------

    Original Message


  • 3.  RE: Can't get MXLoader to work with LDAP

    Posted 10-12-2022 10:25
    So I figured it out.  In the spreadsheet I had the OSLC Service context root incorrect.  For the REST service it needs to match the mxe.oslc.restwebappurl system property.  I was accidently pointing to the URL in this system property mxe.oslc.webappurl.

    Part of my error was in our test environments the URL's are https://<SERVER>/maxrestdev/oslc/  or https://<SERVER>/maxreststg/oslc/ because we have multiple Maximo environments on one instance of WebSphere. 

    For production we have it as  https://<SERVER>/maxrest/oslc/ 

    To add to the confusion there is a non-REST service https://<SERVER>/maximo/oslc/ (i.e. mxe.oslc.webappurl)

    So by accident I typed it in correctly for our test environments and not production.  

    Thanks for your response.  I appreciate you taking the time to reply!




    ------------------------------
    Eric Burkland
    San Diego County Water Authority
    ------------------------------

    Original Message


Related Content