Skip to Content Information Center
Lexmark M3150

Lexmark M3150

Not your product?

eDAS and RegisterME escalation requirements

Before proceeding, make sure to fill out the Main escalation information requirement and gather the eSF applications primary escalation requirements.

Gather the additional requirements specific to eDAS and RegisterME issues.

Requirement and relevanceHow to obtain

Is Pharos Blueprint or Uniprint being used?

 

The information is used for simulation and analysis.

Enduser provided

Pharos version used

 

The information is used for simulation and analysis.

Enduser provided

Screenshots of "Settings" screen, i.e. general charging, related functions, etc.

 

The information is used for simulation and analysis.

Navigate to Pharos System Blueprint Administrator > Device Management > Terminals > Settings tab.

Authentication Script used

 

The information is used for simulation and analysis.

Enduser provided

Screenshot of "Lexmark iMFP / iPR Configuration" screen

 

Make sure to Enable Authentication. First Authentication Token and Second Authentication Token match with the Authentication Script. Refer to the following table:

Navigate to Pharos System Blueprint Administrator > Device Management > Terminals > Lexmark iMFP / iPR Configuration tab.

Authentication Script

Enable Authentication

First Authentication Token

Second Authentication Token

Basic

Unchecked

Username

Password

Card Alternate

Checked

Username

Password

Card ID

Unchecked

CardSwipe

None

RegisterME

Checked

Username

Password

Username and Password

Unchecked

Username

Password

Username

Unchecked

Username

None

Terminal Type (.xml) files used (if available)

 

The information is used for simulation and analysis.

Enduser provided

You must verify whether Lightweight Directory Access Protocol (LDAP) server or Microsoft Active Directory is used for authentication.

 

The information is used for simulation and analysis.

Enduser provided

TaskMaster.log after reproducing the application error or authentication error (if any occurs)

 

The information is used for simulation and analysis.

This log is available under installed directory\Logs\; e.g., C:\ProgramData\PharosSystems\Blueprint\Logs\TaskMaster.log"

Value of User Attribute

 

This can be used as a filter to find user’s LDAP/AD entry.

Enduser provided

For LDAP:

  • uid
  • cn

For Active Directory:

  • sAMAccountName

Value of objectClass

 

This can be used as a filter to find user’s LDAP/AD entry.

Enduser provided

For Active Directory or LDAP:

  • user
  • organizationalPerson
  • person
  • top

For LDAP only:

  • inetOrgPerson

If Register ME application is used in Active Directory environment, and you prefer not to have adminDn and adminPassword in clear text in the Authentication Script, check whether you are using the correct settings

 

The information is used for simulation and analysis.

Set the following:

  • ~ string adminDn = null;
  • string adminPassword = null;
  • AuthenticationTypes authenticationType = LdapUtils.AdSecureAuthType;
  • ~ LdapSearchResult result = LdapUtils.FindAdUser(serverUri, adminDn, adminPassword, authenticationType, filterFormat, filterParameters, resultProperties, password);
  • ~ You will also need to set the Pharos Task Master service (on Pharos BP server) to run under domain account.

Also, navigate to Control Panel > Administrative Tools > Services > Pharos Task Master (service) > right-click and select Properties > Select Log On tab > Select Log On as this account > enter Account Name; e.g., accountname@ad.indiadev.lexmark.com > enter Password and Confirm Password fields > click Apply > Restart Pharos Task Master (service).

Note:  If RegisterME application is used:

  • Make sure the same User Attribute is used on application Configure webpage.
  • Make sure the same User Attribute is used while initializing filterFormat and resultProperties in the Authentication Script.

      • Example for LDAP

    • ~ string filterFormat = "(&(objectClass=inetOrgPerson)(uid={0.EN_US}))"
    • ~ string[] resultProperties = new string[] { "uid"}

      Example for Active Directory

    • ~ string filterFormat = "(&(objectClass=user)(sAMAccountName={0.EN_US}))"
    • ~ string[] resultProperties = new string[] { "sAMAccountName" }
  • Make sure the same objectClass is used while initializing filterFormat in the Authentication Script.

      • Example for LDAP

    • ~ string filterFormat = "(&(objectClass=inetOrgPerson)(uid={0.EN_US}))"

      Example for Active Directory

    • ~ string filterFormat = "(&(objectClass=user)(sAMAccountName={0.EN_US}))"
  • Make sure Mail Attribute (on application Configure webpage) contains some value which is present on LDAP/AD server.

      • Example for LDAP

    • ~ mail

      Example for Active Directory

    • ~ userPrincipalName
  • Make sure correct Port is used on application Configure webpage.

      • Example for LDAP or Active Directory without SSL

    • ~ 389

      Example for LDAP or Active Directory with SSL

    • ~ 636
  • Make sure you have set Enable SSL and SSL Certificate fields correctly on application Configure webpage.

      • Example for LDAP or Active Directory without SSL

    • ~ Enable SSL should be unchecked and No SSL Certificate should be uploaded

      Example for LDAP or Active Directory with SSL

    • ~ Enable SSL should be checked and a Valid SSL Certificate should be uploaded
  • Make sure correct Port is used when initializing serverUri in the RegisterME Authentication Script.

      • Example for LDAP without SSL

    • ~ string serverUri = "LDAP://directory.lex.lexmark.com:389/ou=Employees,o=Lexmark"

      Example for LDAP with SSL

    • ~ string serverUri = "LDAP://directory.lex.lexmark.com:636/ou=Employees,o=Lexmark"

LEGACY ID: FA993
Was this article helpful?


Related content

Top