Project Vienna: UPN syncing[BETA]
Prevent username clashing when syncing
In 19.2 PaperCut NG/MF sync usernames across multiple active directory domains using the User Principal Name (UPN), avoiding username clashing.SIGN UP FOR BETA
The benefits of UPN username syncing
Better identification across multiple domains
User Principal Names (UPN usernames for short) do away with finicky issues found in legacy syncing methods.
For example, PaperCut NG and MF sync via sAMAccountName by default – so 'mary.jane' in domain A is considered the same user as 'mary.jane' in domain B. Not ideal.
UPN usernames, though? They're designed to keep pesky ID crossover and clashes at bay.
Easier authentication that's widely adopted
Our partners use UPN usernames in their multi-domain environments ñ and for good reason:
- They're conveniently formatted like regular email addresses, i.e. they're made up of a log-on name, a separator (@ symbol), and a domain name.
- They're easy to remember – and can even be the same as the user's email. UPN suffixes can also be configured to shorten usernames in the case of long domain names.
- They're used by Active Directory Federation Services and other federated identity providers.
Windows Active Directory is supported for Project Vienna right now. Let us know in the feedback section below if you're interested in others such as Azure AD and Google Cloud Directory.
Certainly! As long as the user has the email address field populated in PaperCut.
Yes, but right now it's not built into the user interface. You'll need to work with our solutions team to get things transitioned smoothly. Please reach out in the contact section below.
Sure thing! The client OS support does not differ from what PaperCut currently offers.
Of course! End users can login to Mobility Print with their UPN username.
As the feature is still in early beta stage we would like to work with you to determine the best way to set things up for your environment. See below contact section to reach out.