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

Question

Question

Device licenses on tablets

asked on April 2, 2018 Show version history

Looking for a solution to license a tablet for use by multiple users in the same way as a PC.  What I see in the help files says that a device license can't be used with Web Client, so I'm not sure this makes it viable solution for my use case.

But, is there way to license the tablet and provide users with repository licenses to LF and have them access via the LF Mobile App authenticating under a device license?  Or must the users logging into LF Mobile App have independent named user licenses of their own?

Thoughts?

1 0

Answer

SELECTED ANSWER
replied on April 2, 2018

This is not supported at the moment (with or without LFDS). Device licenses were designed for scanning stations for users who don't interact much with the repository. The recommended way of handling tablet users is assigning user licenses for everyone.
If you have some use case that would mandate using device licenses please share it with us, as it doesn't seem hard to support but no promises are made this would be approved.

0 0
replied on April 3, 2018 Show version history

USE CASE:

We have mill operators who do not have any individualized network presence on our system.  They use a generic login to our network and proprietary feed production systems.  This is due to the fact that production is tracked based on jobs running.  These jobs could be handled by one or more operators over one or more shifts.

The operators must evaluate equipment in the mill for air quality, leakage, and general condition throughout a shift, weekly, and monthly.  We would like to deploy a tablet that would be user agnostic to allow for entry of that information into prepared Laserfiche Forms.

The generic login they currently use has rights to the repository and to Laserfiche Forms but not to LF Mobile App.  (This is to prevent a user from downloading Laserfiche to a personal device and getting access to corporate data.)  We also spun off a separate instance of LF Web Client in IIS to prevent access externally using this login.

But, we still want these users to have access via a mobile device to complete forms.  This is where the question about device licensing and it's corollary (https://answers.laserfiche.com/questions/138984/Define-allowed-devices-to-Laserfiche-Mobile-App#repliestomain) regarding identifying devices to LF mobile as Allowed devices originated.

0 0
replied on April 4, 2018

Thank you for sharing your use case for device licenses, although it sounds like you need Forms participant license? I would check that in a Forms Answers forum.


We are currently looking at the possibility of white listing devices (and in the process of implementing white listing user accounts) that can access repositories and forms.


However better solution would be using an MDM product (Laserfiche doesn't recommend any specific vendor) where you could push MDM profiles and set up app-tunneling (per-app vpn) so only devices that have your profile pushed to them can access your servers (Forms, AppServer).
 

0 0
replied on April 5, 2018

Barna,  How does Forms participant license assist in this case?  Login is to LF Mobile App or via Browser on the device?

You mentioned MDM product to sandbox the LF Mobile app, correct?  Just want to make sure I have the correct information to start the discussion internally, thanks!

0 0
replied on April 5, 2018

You should get forms licensing advise from the Forms group or your VAR. A brief description of Forms licensing is at: https://www.laserfiche.com/support/webhelp/Laserfiche/10/en-us/administration/Default.htm#../Subsystems/Forms/Content/Administration/Forms-Licensing.htm


Since you mentioned "user-agnostic" and limited users only submitting forms, Forms Portal or participant users come to mind. However you are correct, that only applies to accessing Forms from a browser.

One mobile app feature that might be useful is the ability to lock offline forms - this is for "kiosk" situations when the user doesn't authenticate to submit forms (which get later submitted online when somebody logs in from the device.)
See the "To lock an offline forms" in https://www.laserfiche.com/support/webhelp/laserfichemobile/10/en-us/lfmobile/lfmobileadmin.htm#App_Topics/Offline-Forms.htm?Highlight=passcode

 

The mobile app server configuration page allows allowing/denying of repository users and the same is being implemented for Forms users
(see Authentication section of https://www.laserfiche.com/support/webhelp/laserfichemobile/10/en-us/lfmobile/lfmobileadmin.htm#Installation_and_Configuration/Configuration_Page_Connection.htm%3FTocPath%3DConfiguration%2520Page%7CConnection%7C_____0 )

Device white or black listing (and mobile security in general) is much better handled through MDMs (sandboxing the app) 
https://www.appconfig.org/ has MDM vendors that support app-tunneling. 
Intune also seems popular (https://docs.microsoft.com/en-us/intune/vpn-settings-configure)

1 0
replied on April 6, 2018

Barna,  thanks for the options regarding how to proceed with our use case. 

0 0
replied on February 28

Hi Michelle, could you please help me with your update for the case with the procedure implemented to solve your question...¿?

Thanks! 

0 0
replied on February 28

Robinson, we do not currently have a procedure implemented that allows use of the tablets in the mills.  This is part of a larger infrastructure build-out for which we are still planning.

1 0
replied on February 28

Michelle, ok no problem, but if you have further information and you could share it with us would be very helpful.Thanks for you answer!.

0 0

Replies

replied on April 2, 2018 Show version history

The way tablet devices connect is through a web client (Mobile, Web Access, or WebLink), so as per the documentation, they cannot be used as Named Devices.  To use a Device License, the connection must come from the LF Windows client or a SDK application.

1 0
replied on April 2, 2018

I can be wrong, but I don't think an iPad or Android tablet would be able to be licensed (yet). I would try it instead with a Windows tablet and see if it works using the Windows Client. 

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

Sign in to reply to this post.