nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Getting 401: Unauthorized error

GlenW

I have created a WCF web service that acts as a "front-end" for other applications to use to create workspaces. This WCF web service uses the IWOVServices.CreatWorkspace to do the work.

I installed this service on a Windows 2003 server and it works fine. However, when I install it on our production 2003 server which also contains our Worksite Web installation, I get 401: Unauthorized errors.

I'm suspicious that it has something to do with the fact that my service and IWOVServices are on the same box. Does anyone have any ideas?

Here is my call to the IWOVServices:

Dim wsServices = New IWOV_SVC.IWOVServices

'> Login to web service as NRTAdmin
wsServices.Credentials = New Net.NetworkCredential(DMSGlobals.Admin_User_Name, _
DMSGlobals.Admin_Web_Password, _
DMSGlobals.MMDomain_Short)
wsServices.PreAuthenticate = True
Dim outMsg As IWOV_SVC.CreateWorkspacesOutput = wsServices.CreateWorkspaces(inMsg)

Find more posts tagged with

Comments

hks

WorkSite Web Service only accepts Windows Authentication. Is the NRTADMIN user a Windows User ?
If not try with a windows user that has the same user name in WorkSite.

_test2.rptdesign

GlenW

WorkSite Web Service only accepts Windows Authentication. Is the NRTADMIN user a Windows User ?
If not try with a windows user that has the same user name in WorkSite.

Yes, NRTAdmin IS a Windows user.

guido1

WCF is very particular about things like authentication. Are you defining the WCF wrapper service you have in code, or declaratively in a config file?

In any case, can you post the client endpoint definition for connecting to the WorkSite asmx web service? Also include the binding configuration, as that defines the authentication model in WCF

GlenW

We finally solved the problem. My engineering staff did some smoke and mirrors with the website setups that I didn't fully follow, but the 401 error went away and it's all working now.

I think they created a virtual directory under the website in IIS in which my service was running that pointed back to the IWOVServices service in it's website.