Difference between revisions of "Docs/Mapping/Autologin"

From Userful Support
< Docs‎ | Mapping
Jump to navigationJump to search
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{Public Support Wiki}}
 
{{Public Support Wiki}}
 
{{DISPLAYTITLE:
 
{{DISPLAYTITLE:
Station Mapping: Autologin
+
Mapping: Autologin
 
}}
 
}}
{{CopyrightNotice|{{REVISIONYEAR}}}}
+
{{CopyrightNotice|{{CURRENTYEAR}}}}
 
__NOTOC__
 
__NOTOC__
  
Line 9: Line 9:
 
'''Autologin''' automatically starts (and logs-in) a native Linux user session for specified users.
 
'''Autologin''' automatically starts (and logs-in) a native Linux user session for specified users.
  
Points to consider before using '''Autologin''' session container:
+
Points to consider before using '''Autologin''' source:
 
* No need to pre-create the users. Autologin will automatically create users as required for the sessions.
 
* No need to pre-create the users. Autologin will automatically create users as required for the sessions.
* For multiple sessions on multiple stations, use the station variable (%STATION_ID%) to include the station number in the username.
+
* For multiple sessions on multiple displays, use the display variable (%DISPLAY_ID%) to include the display number in the username.
* If a fixed username is used (without a station variable), do not map multiple stations to this session container. User settings may become corrupt by doing so. The system will attempt to detect if a session for the same user is started and prevent it but a number of factors may cause this error detection not to work.
+
* If a fixed username is used (without a display variable), do not map multiple displays to this source. User settings may become corrupt by doing so. The system will attempt to detect if a session for the same user is started and prevent it but a number of factors may cause this error detection not to work.
 
* With Autologin (unlike cloud desktop) user settings are saved and retained from one session to the next.  
 
* With Autologin (unlike cloud desktop) user settings are saved and retained from one session to the next.  
** Note: If a user account (e.g., station_1, station_2, etc.) becomes corrupted, you can login as root user and delete the user e.g. <tt>/usr/sbin/userdel station_num</tt>. The deleted user will automatically be re-created when the station restarts.
+
** Note: If a user account (e.g., display_1, display_2, etc.) becomes corrupted, you can login as root user and delete the user e.g. <tt>/usr/sbin/userdel display_num</tt>. The deleted user will automatically be re-created when the display restarts.
* Adjust the prefix to create create usernames that differ more than just by station number or if you are creating multiple Autologin session containers. You can use whichever prefix is best suited to your application (e.g. "student", "teacher", etc).
+
* Adjust the prefix to create usernames that differ more than just by display number or if you are creating multiple Autologin sources. You can use whichever prefix is best suited to your application (e.g., "student", "teacher" etc).
  
<br clear="all" br>
 
  
==Station Mapping: Creating a Autologin Session Container ==
+
==Mapping: Creating the Autologin Source ==
 
+
[[File:Autologin.png|right|400px|thumb|Creating Autologin Source]]
'''Station Mapping''' allows you to bind a specific station to session containers. To create the "Autologin" session container, do the following:
+
'''Mapping''' allows you to bind a specific display to source. To create the "Autologin" source, do the following:<br>
 
+
<br>
[[File:Autologin.png|right|400px|thumb|Creating Autologin Session Container]]
 
 
<ol start="1">
 
<ol start="1">
<li> Click on <tt> Station Mapping > New Session Container </tt> button. From the drop-down menu select "Autologin" as preferred session container type and give it a name.
+
<li> Click on <tt> Mapping > New Source </tt> button. From the drop-down menu select "Autologin" as preferred source type and give it a name.</li>
 
+
<br>
<li>Enter "Username" (The username provided can contain a variable to allow different users to be logged on to different stations. The variable will be replaced by the station number).</li>
+
<li>Enter "Username" (The username provided can contain a variable to allow different users to be logged on to different displays. The variable will be replaced by the display number).</li>
 +
<br>
 +
<li> Select the Session type from the drop-down. </li>
 +
<br>
 
<li>Click "OK" to complete the process.</li>
 
<li>Click "OK" to complete the process.</li>
 
<!--
 
<!--
Line 36: Line 37:
 
<br clear="all" br>
 
<br clear="all" br>
  
==Map Stations to Autologin Session Container ==
+
==Map Displays to Autologin Source ==
  
[[Image:Autologinsession.png|right|700px|thumb|Autologin Session Container]]
+
Once source is created, displays can be "mapped" or assigned by simply dragging-and-dropping the display icons to the Autologin source.
Once session container is created, stations can be "mapped" or assigned by simply dragging-and-dropping the station icons to the Autologin session container.
+
As with any source, you can also add Autologin source to a "Welcome Screen" thus making it one of several choices available to the user.
As with any session container, you can also add Autologin session container to a "Welcome Screen" thus making it one of several choices available to the user.
 
 
<br>
 
<br>
 
<br>
 
<br>
Line 48: Line 48:
  
 
==Related Links==
 
==Related Links==
* [[Docs/Station Mapping | Station Mapping Guide]]
+
* [[Docs/Mapping | Mapping Guide]]
  
 
{{forcewhitespace}}
 
{{forcewhitespace}}
[[Category:Station Mapping]]
 
 
[[Category:Docs]]
 
[[Category:Docs]]

Latest revision as of 19:38, 24 April 2018


Copyright © 2020 Userful Corporation. All rights reserved.
(Updated 2018.04.24)


Introduction

Autologin automatically starts (and logs-in) a native Linux user session for specified users.

Points to consider before using Autologin source:

  • No need to pre-create the users. Autologin will automatically create users as required for the sessions.
  • For multiple sessions on multiple displays, use the display variable (%DISPLAY_ID%) to include the display number in the username.
  • If a fixed username is used (without a display variable), do not map multiple displays to this source. User settings may become corrupt by doing so. The system will attempt to detect if a session for the same user is started and prevent it but a number of factors may cause this error detection not to work.
  • With Autologin (unlike cloud desktop) user settings are saved and retained from one session to the next.
    • Note: If a user account (e.g., display_1, display_2, etc.) becomes corrupted, you can login as root user and delete the user e.g. /usr/sbin/userdel display_num. The deleted user will automatically be re-created when the display restarts.
  • Adjust the prefix to create usernames that differ more than just by display number or if you are creating multiple Autologin sources. You can use whichever prefix is best suited to your application (e.g., "student", "teacher" etc).


Mapping: Creating the Autologin Source

Creating Autologin Source

Mapping allows you to bind a specific display to source. To create the "Autologin" source, do the following:

  1. Click on Mapping > New Source button. From the drop-down menu select "Autologin" as preferred source type and give it a name.

  2. Enter "Username" (The username provided can contain a variable to allow different users to be logged on to different displays. The variable will be replaced by the display number).

  3. Select the Session type from the drop-down.

  4. Click "OK" to complete the process.


Map Displays to Autologin Source

Once source is created, displays can be "mapped" or assigned by simply dragging-and-dropping the display icons to the Autologin source. As with any source, you can also add Autologin source to a "Welcome Screen" thus making it one of several choices available to the user.

Note: Changes will not take effect until the "Apply" button is clicked.

Related Links