How to execute an intent conditioned by a "special" action

R
Remy
Zollner Elektronik AG

Hi all,

I'm looking to execute an sendintent conditioned by a successful "shared device" login...is this possible?

Basically I want to manage the "softkeys" from the navigation panel conditioned by the "Shared Device status".

Without a logged user: "all off" / with one connected : "all on".

3 years ago
SOTI MobiControl
ANSWERS
MD
Matt Dermody Diamond Contributor
3 years ago

I haven't actually deployed Shared Devices before but my understanding of the concept is that after a user is logged in the device can be automatically relocated into a given group/folder. Once in that group/folder the device can be provisioned with whatever configuration payloads like Profiles, Policies, Rules, etc that are assigned to that folder. After the user logs out the device is moved back into a staging folder of sorts which has different payloads assigned. Utilizing this mechanism you could assign a configuration or Package based Profile to the destination folder, and then have that unassigned once the device is logged out. I do not think you need to do anything fancy in trying to detect the logged in vs logged out status as a trigger mechanism as the mere presence of the device in a given folder is what registers what status that it is in. Instead of trying to query to determine if a device is logged in, instead just apply whatever configuration settings you want to have active for logged in devices to the destination folder that the logged in devices are automatically relocated into. Then have that unassigned and reversed whenever the devices leave that group. 

OA
Ozan Acikalin
3 years ago

Like Matt already explained you can relocate your devices to a different group with different policies. So you can have policy_A on logged out devices and policy_B on logged in devices. But make sure that the target group is not inheriting any other profiles.

Also remember that your devices are always moved back to the root group and not the device group they were moved from.

R
Remy
3 years ago

Thanks for your feedback! The idea behind my request is that I'm trying to "secure" the access to the device and not "really" to use the "shared-device" functionality.
Maybe you know another way where I can force a user login "check". We have more than one app in our KIOSK used by more employees with an in-app authentication and there are some concerns related to the security layer of the usage.

OA
Ozan Acikalin
3 years ago

You can run the shared device login screen as a single app kiosk mode. When a user logs in then the device can move to your KIOSK with the apps your employees use. Then you can set the option that mobicontrol should clear the managed app data when a user logs out. The device will then move back to the single app kiosk mode where the next user can log in.

Another way of some kind of user authentication is not available (as far as i know). The shared device feature should be able to cover all your needs.

K
KCMOD@SOTI
3 years ago

Hello Remy,

Thank you for posting on SOTI Central!

I can see that SOTI Central community provided you with answers and suggestions. 

Please let us know if the provided suggestions helped you to resolve your issue/fulfilled your request?


Regards,
Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net

R
Remy
3 years ago

Hi,

It's hard to say at the moment. I understand the limitations within I can "move". What we really need is a simple "log in/lock/log out" functionality "over" a KIOSK Mode via Kerberos without using the "whole underlying process of a real shared-device scenario".

RC
Raymond Chan Diamond Contributor
3 years ago

Hi Remy,

If your primary intention is to secure the device, then you should have given the exact device brand/model of interest and the current loopholes found.

If you have found some script (using sendintent commands or so) to disable/enable soft keys as your way to secure your device, then check if you can have the script executed (e.g. with pre-script in a file-sync rule)  whenever your device gets log out (and relocated to the parent/root device-group).  Use similar approach to arrange a different script to be executed whenever the device gets successfully logged in and relocated to its targeted device-group associated with the shared-device scheme.