Can not log into the /ipcon console

  • 7020147
  • 01-Jun-2017
  • 05-Mar-2019

Environment

Micro Focus iPrint for OES 2015SP1

Situation

Logging into the /ipcon console (https://<iPrintApplianceAddress>/ipcon), fails with a message of invalid credentials. The same user can successfully log into the /psmstatus page and iManager.

Resolution

  1. Apply the OES 2015 SP1 iPrint updates
  2. Delete the iPrint mobile tomcat  work directory:
    • rm -r /var/opt/novell/iprint-tomcat/work
  3. Restart mobile tomcat and Apache instances:
    • rcnovell-iprint-tomcat restart;rcapache2 restart
  4. Wait one minute, then log back into the /ipcon tool.

Cause

Cause 1: Tomcat cache corruption
Cause 2: Timing issue between iprint-tomcat and apache
If eDirectory or iprint-tomcat have been restarted without having also restarted Apache, the services won't properly communicate with each other. 

Additional Information

If the RESOLUTION steps don't resolve the problem or if the resolution doesn't doesn't apply to your environment, then the following information can be helpful in troubleshooting or resolving ipcon login issues:
  1. Search for a duplicate admin named objects in the Tree
    • Go to iManager -> click the View Objects button (blue magnifying glass button along top) -> Search tab -> Search for the name admin
    • Does more than one admin object show? Note: this admin object could be a user, group, ou, workstation object, DNS/DHCP object, etc.  If more than one admin object shows, your 3 options are:
      • Log in with the fully qualified LDAP name
        • Example
        • cn=admin,o=myCompanyOrg
      • Delete the extra admin objects (do not delete the tree admin account)
      • Rename the extra admin objects (do not rename the tree admin account)
  2. Ensure the OES Common Proxy user is assigned as an ACL to the Print Manager object.
    • Go to iManager -> iPrint -> Manage Print Manager -> Access Control -> add the cn=OESCommonProxyUser_myserver,o=myCompanyOrg user to the "Manager role:"
      • cn=OESCommonProxyUser_myserver,o=myCompanyOrg is an example. myserver will be replaced with the server object name and the context will be the context where the server object resides.
  3. Ensure the /etc/opt/novell/iprint/conf/iprintconf.properties file is properly configured.
    • If the /ipcon page has never successfully been logged into, then ensure mobility_addon_configured= line shows false.
    • Restart the iPrint Mobile service
      • rcnovell-iprint-mobile restart
    • Note: For the iPrint Appliance ,which does not have an ipcon page, the mobility_addon_configured= should always be true.
  4. Ensure the OES Common Proxy user is working correctly.  See this Novell Cool Solution to repair that object.
  5. Authenticate to the auth page (https://<ip>/auth) and check /var/log/messages
  6. View the license file:
    • less /etc/opt/novell/iprint/licenseKeys/license.xml
  7. Test iprintman authentication:
    • iprintman psm -l -u cn=admin,o=<OrganizationName>
  8. Test the OES Common Proxy login:
    • Run these two commands:
      • /opt/novell/proxymgmt/bin/cp_retrieve_proxy_cred username
      • /opt/novell/proxymgmt/bin/cp_retrieve_proxy_cred password
    • Authenticate with the OESCommonProxy user:
      • iprntman psm -l -u cn=OESCommonProxy_<serverName>,ou=<OUname>,o=<Oname>
        • provide the password revealed form the cp retrieve proxy cred password command above.
  9. Capture iprintmobile debug log information:
    • Within the /var/opt/novell/iprint-tomcat/webapps/iprint/WEB-INF/classes/logging.properties
      • Change .level=WARNING to FINE
    • Restart the iPrint Mobile service
      • rcnovell-iprint-mobile restart
    • Observe the /var/opt/novell/log/iprintmgmt/iprintman0.log log file while attempting the authentication.
  10. Ask Micro Focus Support for an updated .war file which resolves a known issue with /ipcon logins.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.