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; } } }

Login [NRTSession ][TrustedLogin ]Access denied

Jagann

On system1, Web Service has been installed.

On system2, Web Server has been installed.

In System1, Web Service Login web method is given. In this Username and Password login works but Trusted Login fails.

We have Used TrustedLogin2 method (Web Service on System1) passing Accesstoken received from Web server (installed on System2).

is set in both Web Service and Web Server web.config files.

In debug mode, Invalid handle exception is thrown when try to access Web Service after passing Server Name and accesstoken for TrustedLogin2.

We have tested with TrustedLogin2 /TrustedLogin method also it does not work. Error Trustedlogin Access denied exception is thrown.

Note:
We have configured a domain user in WorkSite Database by specifying NOS type and Container as domain name.
we have tested with DeskSite 8.0/8.2 Trusted login, it works fine.

Is there any setting to be done at WorkSite Server and Client end.
Or any registry setting in WorkSite Server?
Any specific settings for TrustedLogin() and TrustedLogin2() methods?

Find more posts tagged with

Comments

jny

If you're using the Trusted Logon to connect to a dms from within a web app, you will need to call the TrustedLogin2 Method which accepts an argument of a token of the user who has logged on to the local machine. This is the C# function I use to get the user access token:

sess.TrustedLogin2(getUserToken(Context).ToInt32());

private IntPtr getUserToken(HttpContext context)
{
return ((HttpWorkerRequest)((IServiceProvider)context).GetService(typeof(HttpWorkerRequest))).GetUserToken();
}

Also, make sure that you have Anonymous Access turned off in your web app.

Jagann

We have Used TrustedLogin2 method (Web Service on System1) passing Accesstoken received from Web server (installed on System2).

Anonymous Access has been turned off in web app (Web Server installed on System2).

Even after turning off Anonymous Access, Trusted Login Access denied message is displayed.

Below code is used to retrieve Client's login details. This is in Page_Load event of default.aspx page.

Dim AccessToken As Long = 0
AccessToken = System.Security.Principal.WindowsIdentity.GetCurrent().Token.ToInt32

AccessToken code is passed as parameter to Login webmethod of Web Server (installed on system1). Here TrustedLogin2(AccessToken) method is used to login.

We created User with NOS as WinNT (3) in WorkSite Database Administration.
We created other external user as well in WorkSite Database Administration.
Even with these two users we are not able to Login as Trustedlogin.

When we access Web Service Login webmethod and pass Access token to TrustedLogin2 in code of web app running in .Net IDE, we are getting exception as "The handle is invalid".

Note in our web app, two Login options are given. User can login to any of the Login option
(1) Username & Password Login
(2) Trusted Login

Please provide sample web application code or document to use TrustedLogin2 for Web application.

Is there any registry settings for TrustedLogin2?

Is there any settings at WorkSite Server or WorkSite database for web app access of TrustedLogin2?

jny

There is a key to specify the type of trustedlogin, but it is not specific to TrustedLogin2(); it's used just for the imanage.dll to know the type of trustedlogin thus it just needs to be set on the calling machine. However, if you have Windows as the login credentials, then this is the default setting thus there shouldn't be any need to set it explicitly in the reg key. It is only when you have ADS or NDS that you need to explicitly set it. You would need to contact Technical Support to find this key as I don't remember off hand. I have Windows thus I don't bother with it.

There is also no specific configuration just for the Trustedlogin2 method. It's the same as using TrustedLogin Method except you use the TrustedLogin2 for web app as that's what IManage.dll uses for web apps. You should, however, have TrustedLogon enabled in the WorkSite DMS Service Manager, and that your Windows users are already added to the database via the IManAdmin program.

I don't have any web app right now. I already provided the C# function to demonstrate how you should retrieve the HttpContext thus you should try getting that form within your VB.Net app.

dabird

Did you set up impersonation in the web.config file for your web app? By default, WindowsIdentity is running under the context of the ASP.NET worker process, not the user connecting to your application. If you have WorkSite Web installed, you can perform trusted login to verify that TrustedLogin2 works correctly. If you cannot login through WorkSite Web, then you have a configuration issue with your DMS.

Here are a few articles to get you started on web application authentication on MSDN:

How To: Use Windows Authentication in ASP.NET 2.0
ASP.NET Windows Authentication Provider
ASP.NET Impersonation

Below code is used to retrieve Client's login details. This is in Page_Load event of default.aspx page.

Dim AccessToken As Long = 0
AccessToken = System.Security.Principal.WindowsIdentity.GetCurre nt().Token.ToInt32