SOAP WebService NAV 2013 R2 failed using UserName Credential

superpuz

Hi All,

I found that SOAP web service of NAV server instance in NAV 2013 R2 must encrypted using SSL. So I followed the steps found in http://msdn.microsoft.com/en-us/library/ee414240%28v=nav.71%29.aspx. I managed to verify the SOAP web service (by insert this address"https://localhost:7047/DynamicsNAV71/WS/services) only using Windows and NavUserPassword credential type. While using UserName credential type, IE will ask for user name and password, but after filling the username and password in the log on windows correctly, the log on windows will show up again, up to 3 times, and at last leave the page blank.

On Event viewer there's an Audit Failure such as bellow:

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          5/19/2014 4:00:31 PM
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      NAVSVR.srm.net
Description:
An account failed to log on.

Subject:
	Security ID:		NULL SID
	Account Name:		-
	Account Domain:		-
	Logon ID:		0x0

Logon Type:			3

Account For Which Logon Failed:
	Security ID:		NULL SID
	Account Name:		administrator
	Account Domain:		srm

Failure Information:
	Failure Reason:		Unknown user name or bad password.
	Status:			0xC000006D
	Sub Status:		0xC000006A

Process Information:
	Caller Process ID:	0x0
	Caller Process Name:	-

Network Information:
	Workstation Name:	-
	Source Network Address:	-
	Source Port:		-

Detailed Authentication Information:
	Logon Process:		WDIGEST
	Authentication Package:	WDigest
	Transited Services:	-
	Package Name (NTLM only):	-
	Key Length:		0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
	- Transited services indicate which intermediate services have participated in this logon request.
	- Package name indicates which sub-protocol was used among the NTLM protocols.
	- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
    <EventID>4625</EventID>
    <Version>0</Version>
    <Level>0</Level>
    <Task>12544</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8010000000000000</Keywords>
    <TimeCreated SystemTime="2014-05-19T09:00:31.303966000Z" />
    <EventRecordID>189202</EventRecordID>
    <Correlation />
    <Execution ProcessID="11480" ThreadID="102096" />
    <Channel>Security</Channel>
    <Computer>NAVSVR.srm.net</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="SubjectUserSid">S-1-0-0</Data>
    <Data Name="SubjectUserName">-</Data>
    <Data Name="SubjectDomainName">-</Data>
    <Data Name="SubjectLogonId">0x0</Data>
    <Data Name="TargetUserSid">S-1-0-0</Data>
    <Data Name="TargetUserName">administrator</Data>
    <Data Name="TargetDomainName">srm</Data>
    <Data Name="Status">0xc000006d</Data>
    <Data Name="FailureReason">%%2313</Data>
    <Data Name="SubStatus">0xc000006a</Data>
    <Data Name="LogonType">3</Data>
    <Data Name="LogonProcessName">WDIGEST</Data>
    <Data Name="AuthenticationPackageName">WDigest</Data>
    <Data Name="WorkstationName">-</Data>
    <Data Name="TransmittedServices">-</Data>
    <Data Name="LmPackageName">-</Data>
    <Data Name="KeyLength">0</Data>
    <Data Name="ProcessId">0x0</Data>
    <Data Name="ProcessName">-</Data>
    <Data Name="IpAddress">-</Data>
    <Data Name="IpPort">-</Data>
  </EventData>
</Event>

Is there any information what cause this? how to fix this?

Additional Info:
- OS: Windows Server 2012 R2
- NAV: NAV 2013 R2 (Build 36310)
- SQL: SQL Server 2012 SP1
- ADDS, SQL Server and NAV Server Instance are installed in this server.

Edited:
- This only happens on Windows 2012 R2. Everything works fine on Windows 2012.

Administrator

[Topic moved from 'NAV Courses, Exams & Certification' to 'NAV Three Tier' forum]

superpuz

Hi All

I haven't got the solution until now. but I found out that this issue happens on NAV 2013 R2 installation on Windows 2012 R2. I cannot call the web service while the NAV service instance using UserName credential type.

I just wonder if anyone having the same problem and got the solution?

I've been working with the Microsoft support team but no luck.

superpuz

Dear All,

Has anyone manage to consume NAV 2013 R2's SOAP web sevice on Windows 2012 R2 using UserName credential type?

I failed due to Security audit failure. But it only when I use UserName credential type and using Windows 2012 R2. The same scenario works fine in Windows 2012, so my hunch it is caused by something that Windows 2012 R2 has, but still don't know which one.

superpuz

Someone's just told me that he managed to consume SOAP web service in NAV 2013 R2 CU10 installed on Windows 2012 R2 using UserName Credential type. So I decided to reinstall my NAV with the CU15. but the result is still the same, security audit failure. I assume, it is something to do the domain security or such. Is there any suggestion where to look?

tfenster

I had the exactly same problem but found a solution at least for me: After runnning

netsh http add sslcert ipport=0.0.0.0:7248 certhash=80bdf46682a5cedb64b8457cb3a2eaba4622846c appid={00112233-4455-6677-8899-AABBCCDDEEFF}

with the port for the WebServices (in my case OData) and the certhash as used in the cert thumbprint config it now works for me

superpuz

tfenster wrote:

I had the exactly same problem but found a solution at least for me: After runnning

netsh http add sslcert ipport=0.0.0.0:7248 certhash=80bdf46682a5cedb64b8457cb3a2eaba4622846c appid={00112233-4455-6677-8899-AABBCCDDEEFF}

with the port for the WebServices (in my case OData) and the certhash as used in the cert thumbprint config it now works for me

I believe I've done that many times, delete and add sslcert. Plus the Administration Tool will add the sslcert for us when we save our service instance's configuration in some condition:
1. Specify cert thumbprint w/o any spaces.
2. Enable SSL for SOAP or OData webservice.

Somehow the problem presist in my installation