You are viewing limited content. For full access, please sign in.

Question

Question

Named Devices Through Web Access and Toolkit

Laserfiche Web Client SDK
Updated January 8, 2014
asked on January 8, 2014

We've run into an issue where a client is using named devices.  This allows several non-named users to log in from a Named device machine.  Unfortunately from what I've gathered is this only works through the full client.  When they attempt this through Web Access, web access will not check to see if it's coming from a named device, only the user.  My question is why and if there is a way around this. we have solutions already programmed and implementing using WebAccess scanning URL syntax(not browsing through web access, just scanning portion) and this is impeding the overall solution.  Also we were wondering, we haven't tested it yet, but does the toolkit check to see if it is a named device or not?  Both import and scanning are using windows authentication.  The users are setup in Laserfiche as non-Named windows accounts.  Any help would be appreciated.

 

~Brandon

 

0 0

Answer

APPROVED ANSWER
replied on January 8, 2014 • Show version history

I just wanted to point out that named device licenses cannot be applied to web applications (Web Access, WebLink, etc.) This is a policy that you can further discuss with your Laserfiche Regional Manager.

1 0

Replies

replied on January 8, 2014 • Show version history

All security is checked and enforced by the Laserfiche server; for the most part it doesn't matter what application is trying to create the connection.  Then it becomes clear why Web Access isn't working the way you expect with named device licensing - all connections to the Laserfiche server originate at the Web Access machine, and the machine where the user is located doesn't enter into it.  So you generally don't want to use named devices when you are using Web Access.

 

The same rules apply to the SDK - it's the machine where your application is running that's important.  So a Winforms application can use named users but an ASP.Net application will run into exactly the same problems as Web Access.

0 0
replied on January 8, 2014

Well the solution is already in place and no turning back, are you saying an answer could be to name the WebAccess server as the named device and it would allow connections in?  The SDK would also be in the same boat as it's actually a web application that's running..  

0 0
replied on January 8, 2014

Setting the Web Access server as a named device should allow some connections in, until you hit the relevant limit (which might be 8?).  There is no scaling beyond that as it's not the case that named devices is meant for: http://www.laserfiche.com/support/webhelp/Laserfiche/8.2/en-US/AdminGuide/LFAdmin8_Left.htm#CSHID=Add_Named_Device.htm|StartTopic=Content%2FAdd_Named_Device.htm|SkinName=WebAudit.  Even if it technically can work, I don't know if using a single named device license to provide service to multiple users simultaneously is a violation of the license agreement...  you should check with your sales representative about that.

1 0
APPROVED ANSWER
replied on January 8, 2014 • Show version history

I just wanted to point out that named device licenses cannot be applied to web applications (Web Access, WebLink, etc.) This is a policy that you can further discuss with your Laserfiche Regional Manager.

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...