Affected products 
Click
Properties
in the title section above.
What you will see
Using two different login methods to configure the application results in added usernames (profiles) not being available to the user.
For example:
| Usernames created with... | Followed by usernames created with ... | Results in... |
| LPM premise card authentication selected as login method... | "Local Account Username" authentication selected as login method... | Unavailable profiles when launcing the application. |
Explanation
When the application is configured using a different login method from that of the LPM premise card authentication application, the usernames end up being treated as separate entitites.
The 'local account' username from the application has a different unique ID from the username created with LPM premise card authentication. Hence, these usernames become technically different in the configured profile of the Cloud Connection application, and this results in missing profiles.
This scenario is not likely with most LDAP/network accounts since they seldom utilize two different authentication methods to refer to the same user.
Still need help?
If you need additional assistance, please close this browser tab or go to the Lexmark support site, type your printer model and locate
Get in Touch with Lexmark! for contact information.
NOTE: When calling for support, you will need the following:- Name and version of the solution
- Affected printer model/s
- Printer serial number
Please be near the product/s described in this article to expedite the support process and reduce callbacks.
LEGACY ID: SO8651