RE: How to Authenticate to WCF Service Via VPN

[Steven Cheng [MSFT]]

Hi Schmitz,

Have you got any progress on this issue?

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

From: st*****@online.microsoft.com (Steven Cheng [MSFT])
Organization: Microsoft
Date: Thu, 17 Jul 2008 07:36:48 GMT
Subject: RE: How to Authenticate to WCF Service Via VPN

Thanks for your reply Schmitz,

So assigning the default networkCredential not work. Currently as for VPN
connected client, is it using the same user account as when you tested via
a non-VPN client? If the code work when not use VPN but fails (with
identical account) via VPN connection, we may need to focus on the VPN
part. Otherwise, I think the problem is still the client credential not
correctly be recognized by the server-side. for current security context,
you can use the following code to check it:

System.Security.Principal.WindowsIdentity.GetCurre nt()

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[Henry Staples]

Steven,

I'm having a similar issue, but it doesn't involve a VPN.

1) User is logged into SUBDOM1.DOMAIN.GOV
2) Web server 1 is in SUBDOM1.DOMAIN.GOV
3) Web server 2 is in SUBDOM2.DOMAIN.GOV
3) On both web server apps, NTLM turned on, web.config is for Windows authentication.
4) User connects to .aspx on web server2. In the web page, HttpContext.Current.User.Identity shows NTLM authentication and subdom1\user as who authenticated. All is good.
5) In that same .aspx, trying to connect to a web service on web server 1 by setting webService.Credentials = System.Net.CredentialCache.DefaultCredentials gives a 401 error
6) Move everything on web server 2 to another web server in the SUBDOM1 domain and everything works OK.

It's like there's some sort of issues between SUBDOM1 and SUBDOM2 where it SUBDOM2 says "hey, sure, I can authenticate anyone in SUBDOM1 domain to use this code" but when it passes that authentication over to a server in SUBDOM1 it says "umm, sorry, buddy, but I don't recognize that credential, Unauthorized."

Is there any other way to set these parms or set other settings so the credentials can be passed back over to the web server in SUBDOM1?