Skip to Content Information Center
Lexmark CS728

Lexmark CS728

Card authentication app help resources and suggested troubleshooting tips


The Lexmark Card Authentication App locks out the printer until a user authenticates it with a badge. It secures access to the printer by using a user-defined security server or another printer as a server.

Note:  All features of the application require a license to execute.


Card Authentication 5.0.x includes the following functions and features:

Printer-based badge provider

  • Device Roles
    • Master
    • Backup
    • Client
  • Device Registration (with Registration Retries)
  • Change Role
  • IP Change
  • Badge Enrollment and Verification
  • Synchronization
  • Log in / Log out
  • Status Page
  • Add and Delete Clients
  • Delete Users

Login Screen Settings

  • Use Custom Login Text
  • Login Screen Image
  • Allow Copy without Login
  • Allow Fax without Login

Supported Devices

Card Authentication 5.0.x is supported the following Lexmark devices that possess a minimum 256 MB of memory, the required level of firmware, and that can support card readers. See specific supported printers listed:

Printer ModelFirmware Version


CB.02.042 or later


YK.02.041 or later


ATL.02.042 or later


PP.02.041a or later


PP.02.041a or later

Guides and Help Resources

Troubleshooting Guides

Card Authentication 5.0.x diagnosis topics in this article:

  • List of error messages that appear on the control panel
  • Some settings do not appear in the configuration page for the application
  • Cannot register a client printer on printer-setup issue
  • Troubleshooting tips on other printer-based setup issues


  • Uninstalling / reinstalling the application are not advisable as a troubleshooting solution.
  • All badge registry information and clients' list are deleted together with the application if the device is set as Master / Backup (Printer-based setup) roles. Please perform full migration first, if necessary, and refer to the Administrator's Guide for the instructions.
Error MessageRecommended Action

"Unable to connect to LDAP server."

Verify whether the LDAP settings of the Card authentication's configuration are correct. If Use Address Book setting is enabled, please perform the following:

  1. Navigate to Security > Network Accounts.

  2. Select the account which is at the top in alphabetical order.

  3. Verify if the setup is correct.

Refer to the Administrator's Guide for more information.

"Unable to connect to the User Database."

"An authentication error has occurred."

Update the allowed number of login failures and lockout time.

Note:  This recommendation is applicable only in some printer models. The user may have reached the allowed number of login failures.

  1. From the Embedded Web Server (EWS), click Settings > Security > Login Restrictions.

  2. Update the allowed number of login failures and the lockout time.

  3. Click Save.

Note:  Wait for the lockout time to pass before the new settings take effect.

"This application requires a license to execute."

Make sure that the license is up-to-date by performing the following steps:

  1. Open a Web browser, and then type the following: http://<device IP address>/webservices/vcc/licenses

  2. Search for the key "CardAuth".

  3. From the list, check the license status of the application.

"Cannot find badge ID. Contact your system administrator."

Enabling the Card Registration setting will allow the user to register his/her badge to the badge provider.

Note:  This error message is displayed only when the badge ID is not yet registered to the configured badge provider and Card Registration is disabled.

"Unable to connect to Web server."

Check the SE logs. If you find the following error: The operation timed out

Increase the value of Timeout (seconds) under Web Service Settings of the application's configuration. If you are seeing different error in the SE logs, verify whether the server is up and the printer device is connected to the network.

"Cannot connect to the Identity Service Provider."

Check the SE logs. If you find the following error: The operation timed out

Increase the value of Network Timeout (in seconds) and Socket Timeout (in seconds) under Identity Service Settings of the application's configuration. You can also set the values to 0. If you are seeing a different error in the SE logs, verify whether the Identity (IDP) server is up and the printer device is connected to the network.

Some settings do not appear in the configuration page for the application

Recommended ActionImages

If you are using Internet Explorer, then make sure not to display Intranet sites in Compatibility View.

Open Internet Explorer > Tools > Compatibility View Settings > and make sure to uncheck “Display Intranet sites in Compatibility View”. It is outlined in red in the right-hand image.

Cannot register a client printer on printer-setup issue



Make sure that the master printer or the backup printer is online.


Make sure the master printer and backup printer are properly set up.


As they may have exceeded the allowable number of client printers in the list, delete printers from the list in order to be able to add a client printer. For more information, see “Managing client printers and user accounts” on page 13 of the Administrator's Guide.

Troubleshooting tips on other printer-based setup issues

For other printer-based setup issues…Else…

Make use of the status page. Even if the issue is in the Client device, make sure to get a screen shot of the Master and Backup status pages, apart from getting the corresponding SE debug logs.

In the SE debug log, look for any of these lines:

Setting response to statusCode: xxx


Returning statusCode: xxx

These refer to the return codes for the Services call, which can be any of the following:

public static final int PROXY_STATUS_CALL_SUCCESS = 0; public static final int PROXY_STATUS_NO_ROUTE_TO_HOST = 404; // Connection Exception, inaccessible IP public static final int PROXY_STATUS_NOT_PRINTERBASE = 200; public static final int PROXY_ERROR_NULL_PARAMETER = -1; public static final int PROXY_ERROR_INVALID_URI = -1; // Changeable - starts at 10 public static final int PROXY_STATUS_CHANGE_SUCCESS = 10; public static final int PROXY_STATUS_CHANGE_FAILED = 11; public static final int DEVICEREG_ALLOWED_CLIENT = 12; public static final int DEVICEREG_ALLOWED_BACKUP = 13; public static final int DEVICEREG_DENIED_CLIENT = 14; public static final int DEVICEREG_DENIED_BACKUP = 15; public static final int DEVICEREG_NOTALLOWED_BACKUP = 16; public static final int DEVICEREG_ERROR = 17; public static final int GET_LASTCONTACT_SUCCESS = 18; public static final int GET_LASTCONTACT_FAILED = 19; public static final int PROXY_STATUS_SYNCHRONIZING = 20; public static final int GET_TOKEN_SUCCESS = 21; public static final int GET_TOKEN_FAIL = 22; public static final int GET_IP_SUCCESS = 23; public static final int GET_IP_FAIL = 24; public static final int DEVICEREG_MASTERTASK_STILL_RUNNING = 25; public static final int DEVICEREG_NOTALLOWED_CLIENT = 26;

// BadgeManagement - starts at 30 public static final int PROXY_STATUS_BADGEMANAGEMENT_SUCCESS = 30; public static final int PROXY_STATUS_BADGEMANAGEMENT_FAILED = 31; public static final int BM_NEW_USER = 32; public static final int BM_NEW_USER_REGISTERED = 33; public static final int BM_EXISTING_BADGE = 34; public static final int BM_EXISTING_USER_AUTHENTICATED = 35; public static final int BM_EXISTING_USER_UPDATED_BADGE = 36; public static final int BM_EXISTING_USER_TEMP_BADGE = 37; public static final int BM_AUTHENTICATION_ERROR = 38; public static final int BM_INVALID_CLIENT = 39; public static final int BM_PB_CANNOT_PROCESS_ERROR = 40; // Discoverable - starts at 50 public static final int PROXY_STATUS_DISCOVERY_SUCCESS = 50; public static final int PROXY_STATUS_DISCOVERY_FAILED = 51; public static final int PROXY_STATUS_DISCOVERY_DENIED = 52; public static final int PROXY_STATUS_DISCOVERY_NOBACKUP = 53; public static final int PROXY_STATUS_DISCOVERY_CLIENT = 54;

// Synchable - starts at 60 public static final int PROXY_STATUS_SYNCHABLE_SUCCESS = 60; public static final int PROXY_STATUS_SYNCHABLE_FAILED = 61; public static final int PROXY_STATUS_SYNCHABLE_NODATA = 62; public static final int PROXY_STATUS_SYNC_RESOLVE_SUCCESS = 63; public static final int PROXY_STATUS_SYNC_RESOLVE_FAILED = 64; public static final int PROXY_STATUS_SYNC_RESOLVE_SEND = 65; public static final int PROXY_STATUS_SYNC_RESOLVE_RECEIVED = 66; public static final int PROXY_STATUS_SYNC_DENIED = 67;


Was this article helpful?