Authentication with UPN (MS AD)

Hi Severin,

you can not use the UPN in the form user@domain for the username when logging in into PRTG.

For more information please take a look in the section "Notes and Restrictions" of the "Active Directory Integration" documentation.

Kind regards,
Matthias Kupfer - Team Tech Support

Hi Matthias

Usage of UPN, should be a preferred option! Samaccountname while still in use today is considered legacy. Userprincipalname has been around since Windows 2000. It has the advantages of being able to be set the same as someone's email address, this means people don't need to remember anything except their email and password. In fact Paessler themselves use Email address as the logon for this very forum, showing how effective an email is as the logon name. Email addresses are used as the logon for most services, so making internal systems like AD match the users email address is soemthing a lot of companies do. We do it and we have trained our users to use UPN for everything.

Additionally, while its not been announced yet, it wouldn't be far fetched to a assume a time will come when MS depreciate use of Samaccountname for authentication. Most enterprise grade systems use UPN or allow the use of UPN. Some examples, Grafana, Cisco, snow etc

I would class this as updating a legacy bit of code rather than a feature request. Is this something that can be suggested for future builds of PRTG.

All the best!

Thank you for your inquiry. We already have this "feature" on our internal roadmap, however I can not give you a specific date, when this will be released.

Kind regards, Matthias Kupfer

Hi Matthias, thanks for update. Be great to see that implemented at some point in the future!

+1 to this. Would be extremely useful, especially given SSO is also not an option. My users are much better engaged to adopt products when using the same ID.