Problem using NAVUserPassword in 2013 for authentication

Excepti0nal

I followed this blog because I am trying to use NAVUserPassword authentication instead of the default windows authentication. I get the error listed below when trying to login though. Anyone have an suggestions?

borntobewild

I did have the same problem and I did was delete all certificates I created and perform the steps again. Now it works properly.

I used this link:
http://msdn.microsoft.com/es-es/library ... 70%29.aspx

Excepti0nal

Thank for the reply, sorry Im so late. I am going to try this on one of my test databases and I will let you know if I can get it working.

superpuz

hi!

I get the same error after following the steps from msdn and log in through a client komputer. some said that I need to install the root CA and its revocation list on client's computer. It's done but the error presist. I can log in normally w/o error on NavServer's Windows Client.

The credential type I used is UserName. The client computer is on a workgroup while the NAV server is a Domain Controler.

Is this scenario is possible?

Geff

superpuz wrote:

hi!

I get the same error after following the steps from msdn and log in through a client komputer. some said that I need to install the root CA and its revocation list on client's computer. It's done but the error presist. I can log in normally w/o error on NavServer's Windows Client.

The credential type I used is UserName. The client computer is on a workgroup while the NAV server is a Domain Controler.

Is this scenario is possible?

@Superpuz, did manage to have a work around?

aniish

superpuz wrote:

hi!

I get the same error after following the steps from msdn and log in through a client komputer. some said that I need to install the root CA and its revocation list on client's computer. It's done but the error presist. I can log in normally w/o error on NavServer's Windows Client.

The credential type I used is UserName. The client computer is on a workgroup while the NAV server is a Domain Controler.

Is this scenario is possible?

If you are working in a same domain then you can also use UserName credential instead of NavUserPassword.

/Gaurav