Microsoft Dynamics NAV and Windows Hello PIN

(0) Share

Report

Posted on by Community Member

Hi All,

We have recently moved over to using Windows 10 and Windows Hello with PIN for client logins. The roll out has been smooth but I have come across an issue which I'm struggling with.

NAV is throwing up 'The Service Principal Name (Delegation) configuration has been set incorrectly. Server connect URL: "Our Address". SPN Identity: "Our Message". A call to SSPI failed, see inner exception'.

We went through multiple routes to resolve this including updating the ClientUserSettings.config file under Roaming. The change we made to this file was to make authentication 'UserName' rather than 'Windows'. This then prompted the user to login using their domain details and NAV loaded without issue.

I reset the file to 'Windows' and asked the user to login using their username and password when powering on their computer, this in turn has also resolved the issue.

So, the million dollar questions is - Is there a way for NAV to correctly load WHEN a user has logged on using a PIN with Windows Hello instead of their password?

Version: Microsoft Dynamics NAV 2013 R2 (7.1.37563.0)

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

AJAnsari 5,754 on at

Like (0)

Report

RE: Microsoft Dynamics NAV and Windows Hello PIN

Hi Tombofix,

NAV does not support a PIN based login (yet). Once you are logged into Windows 10 with a password or PIN, having the "Windows" authentication method for NAV helps you pass these credentials through seamlessly to the NAV server without the user having to type this in.

The "UserName" option is not meant to be used the way you are attempting to use it. It is designed for use when an SSL certificate is deployed (and this is an important prerequisite) and the certificate thumbprint is used to configure the NAV Service. This allows users from non-domain-connected machines, devices and applications (or remote users, as an added layer or security) to use the windows credentials by typing them in, and if valid, they can connect to NAV. It will not, however, accept a Windows Hello PIN / facial recognition / fingerprint in place of your Windows 10 password. I can see a route where you could use a third party app to have your fingerprint automatically fill in the password value for you, but that's not what you're looking for (and it isn't native).

Not that you asked, but if you are using O365 / AAD auth (I think it is available with NAV 2013 R2, but not 100% sure; definitely available from NAV 2015 onwards), you can use two-factor auth for O365 and for NAV access.

I hope this helps. If my response has answered your question, please verify by clicking Yes next to "Did this answer your question?"

Was this reply helpful? Yes No
Suggested answer

Zaid Tariq 2,274 on at

Like (0)

Report

RE: Microsoft Dynamics NAV and Windows Hello PIN

Hi,

This seems to be the issue with AD.

Have a look at these link, may be they could be helpful:

dynamicsuser.net/.../service-principal-name-error

msdn.microsoft.com/.../jj551742(v=nav.90).aspx

Was this reply helpful? Yes No
Rashed 3,765 on at

Like (0)

Report

RE: Microsoft Dynamics NAV and Windows Hello PIN

This has nothing to do with using a PIN with windows.

This is an issue on your Active directory. The SPN (Service principal names) are not setup correctly.

On MSDN there is direction on how to fix the SPN. contact your AD admin to fix this.

Was this reply helpful? Yes No