Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Access Rights Manager (ARM) formerly 8MAN > ARM - Knowledgebase Articles > Unable to authenticate ARM username

Unable to authenticate ARM username

Table of contents

Updated Mar 04, 2019

Overview

You have done a fresh installation of ARM and unable to login to either the ARM config or the thin client using an Active Director Domain account and you see the below error in windows logs and pnserver.log. Further, you can only login with local user account to the application.

 

[   1980|SRV12-WSUS  |pnServer    |5176.1| 47|mydomain.com\SYSTEM       |pn.helper.DomainHelper                  |190218|13:36:51.874|Error      ]             DomainHelper.ValidateCredentialLegacy(String userName, String fullQualifiedDomainName, String password): System.UnauthorizedAccessException: No credentials available for Impersonation

--BEGIN-OF-EXCEPTION------------------------------------------------------------

System.UnauthorizedAccessException: No credentials available for Impersonation

   bei pn.security.Impersonation..ctor(WindowsCredential credential, ImpersonationOption options)

   bei pn.security.Impersonation..ctor(ICredential credential, ImpersonationOption options)

   bei pn.helper.DomainHelper.ValidateCredentialLegacy(String userName, String fullQualifiedDomainName, String password)

--END-OF-EXCEPTION--------------------------------------------------------------

Environment

  • Access Rights Manager

Cause

  • It may be because the NetBios name contains a period, so the user in the domain may not be identified. 

Resolution

  • On ARM server open pnserver.config.xml located in the folder: %ProgramData%\protected-networks.com\8MAN\cfg
​​​​<activeDirectory.FqdnToNetBios.8man-demo.local>8man-demo.any</activeDirectory.FqdnToNetBios.8man-demo.local>
<activeDirectory.NetBiosToFqdn.8man-demo.any>8man-demo.local</activeDirectory.NetBiosToFqdn.8man-demo.dings>
  • Add the two lines above at the end and before </config> tag and replace the domain name below with the ones in your Environment.
    • FQDN = 8man-demo.local
    • NetBIOS = 8man-demo.any
  • Restart the ARM service

You should be able to login now.

 
Last modified

Tags

Classifications

Public