One of our clients has a local programmer. He has built a front end application that he is tying into Laserfiche. He is using a single user and since it has session limits he hits them quickly as people use the application. He asked is there a license or way to have his front end application not hit the session limits. I suggested passing the Windows login over to Laserfiche which he has tried and had issues with.
Question
Question
Answer
Getting Windows authentication to work with a web application can be tricky, it requires Kerberos to be configured. One reason the session limit exists it to prevent multiplexing all of your users onto a single license, so there isn't a way around it in your scenario.
Replies
What issues were being encountered with the windows account method?
Here is a bit of his code and a note from him.
_______________
The problem is it's using the iis user
public bool AuthenticateWithRequestId()
{
var ctx = System.Web.HttpContext.Current;
var winId = ctx.User.Identity as WindowsIdentity;
//// if there's no usable identity attached, return a 401
//if (winId == null || winId.IsAnonymous)
//{
// ctx.Response.StatusCode = 401;
// ctx.Response.StatusDescription = "Unauthorized";
// ctx.Response.End();
// return false;
//}
// start impersonating
using (var impersonationContext = winId.Impersonate())
{
// authentication to LF will use the current identity
Session sess = new Session();
sess.ApplicationName = ApplicationName;
sess.LogIn(new RepositoryRegistration(LaserficheHost, RepositoryName));
RaSession = sess;
}
return true;
}