Windows authentication for .NET application

Hi ,In our LAPI .NET application, we have created a Login screen that requires the livelink username and password for accessing the .NET application. Our URL for this is http://localhost/CMS2Eng/default.aspx .Assume http://localhost/CMS2Eng/Pages/Display.aspx?FolderId=14960&DocSource=1 is a URL of another page in the application. If the user directly tries to access this page he is then redirected to the login page for enering his credentials (just like a request handler thats inherited from LLREQUESTHANDLER in the Builder)--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------The user name and password are sent using the function call:Login(txtUserName.Text.Trim, txtPassword.Text.Trim, errStatus)The definition is: Public Function Login(ByVal UserName As String, ByVal Password As String, ByRef errStatus As Integer) As IntegerollSession_LAPI97 = New LLSession(LiveLink_Server, LiveLink_Port, LiveLink_Database, UserName, Password)docInfo = New LAPI_DOCUMENTS(ollSession_LAPI97)userInfo_LAPI97 = New LAPI_USERS(ollSession_LAPI97)entInfo = New LLValue().setAssocNotSet()errStatus = docInfo.AccessEnterpriseWS(entInfo)If (errStatus <> 0) Then//we display error message hereElse//we redirect the user to the designated pageEnd IfEnd Function--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Our current requirement is to make this process as a windows authentication. i.e; Once the user enters his windows user name and password at the windows login screen and now if he tries to access http://localhost/CMS2Eng/Pages/Display.aspx?FolderId=14960&DocSource=1 then he should be allowed into the page without being redirected to the login page.Can you please let me know how should i bypass the login screen and achieve the windows authentication requirement?Any suggestion is greatly appreciated.Thanks

Find more posts tagged with

Comments

Appu_Nair

I beleive you have two options here.One is the function that allows you to get the LLcookie form livelink.What it means is that once you authenticate(You have to login to get the cookie) to the livelink server initially a cookie is issued I belive it is called LLCookie.You can create sessions using that.It is in the documentation in session constructors.There are many examples that allow you to read a cookie.The second more popular method is using livelink's module directoryservices.In this case the users do not get a login screen because the authentication happens at the webserver level and is generally termed SSO.In this case your session is perfomed not at the livelink server port(2099 usually) but at the webserver(usually 80) just like a user issues a URL to login.Lot of examples for that also.Getting the logged in user of windows is proabably the most easy part of this ,a google search will get you lot of examples in VB.NET and C#.

Todd_Pinel

A pattern I use quite often is to move authentication up to the webserver (IIS) by enabling "Integrated Windows Authentication" only for the website in question and disabling "Anonymous Access".This forces every request that comes to the website to be authenticated with your domain server. If the user is using Internet Explorer with the correct settings they will authenticate with your website automatically (SSO), if they are using a browser like Firefox they will be prompted for their domain account login information.If they do not pass this authentication they will not be able to access your website. If they do provide the correct credentials (manually or automatically) they will be served the requested resource they were after.I then use a privileged account to create a session to Livelink and then immediately afterwards make a call to the LAPI "ImpersonateUser" function using the users authenticated username. Every LAPI request after this will be run in the context of the Impersonated User.For you this would mean a couple very small adjustments to your code and IIS configuration.1. Change the way IIS is authenticating usersi.e.) enable only Integrated Windows Authentication2. Change your session creation code to login using a privileged Livelink Account and then immediately afterwards make a call to ImpersonateUser.

Roger_Khanna

I am sure you must have found out the solution to getting SSO LL Session working by now. In case you were facing challenges...i have a code snippet that i can pass it to you which i have been using for my .Net application using C++ and C#.