IntelliDoor GSS - Revision history

NelsonJenkins at 15:25, 12 November 2020

2020-11-12T15:25:34Z

NelsonJenkins at 00:00, 17 September 2019

2019-09-17T00:00:29Z

imported>NelsonJenkins at 21:39, 10 February 2015

2015-02-10T21:39:29Z

imported>NelsonJenkins at 20:45, 10 February 2015

2015-02-10T20:45:56Z

imported>NelsonJenkins at 06:59, 6 June 2014

2014-06-06T06:59:27Z

imported>NelsonJenkins at 06:40, 6 June 2014

2014-06-06T06:40:51Z

imported>NelsonJenkins at 04:16, 24 March 2013

2013-03-24T04:16:51Z

imported>NelsonJenkins: Created page with "The IntelliDoor GSS (Global Security Server) is a tool used to coordinate security settings among many IntelliDoor products. While group control is easiest for limited access,..."

2013-02-25T20:45:10Z

Created page with "The IntelliDoor GSS (Global Security Server) is a tool used to coordinate security settings among many IntelliDoor products. While group control is easiest for limited access,..."

New page

The IntelliDoor GSS (Global Security Server) is a tool used to coordinate security settings among many IntelliDoor products. While group control is easiest for limited access, in some cases it is not possible (autoreturn where the land group is not the group you want to allow, for instance). In this case, if you have many IntelliDoors, the GSS provides a single point where you can list people who should have access.

==Setup==
# Rez the GSS object and open it by right clicking and selecting Open, then double-clicking the "_config" notecard.
# Edit the notecard according to who you want to allow and disallow from all of the doors using this server. Make sure you change the server's name to the same server used by your doors. For more information on the whitelist and blacklist, read the section labeled "WHITELIST/BLACKLIST".
# Save the notecard and close it. The server should automatically load the configuration.
# Reset all doors/components. This can either be done by editing the notecard (to put in the server name, for example) or by selecting the door and going to Tools -> Reset Scripts In Selection (or Build -> Scripts -> Reset Scripts). Make sure the door is fully closed before using the Reset Scripts menu option.

==Whitelist/Blacklist==
The GSS has two security features - a whitelist and a blacklist. When a door (or other component) "subscribes" to a GSS by using the same server name in its _config notecard, it loads these lists upon resetting. 
Those in the whitelist always have access to the door, regardless of the door's local settings. Those in the blacklist will never have access to the door, even if it is unlocked or they have access through an Everyone or Group setting. 
The lists are only limited by memory - theoretically, the system should handle more than 100 names easily. 
NOTE ON NAMES: The IntelliDoor system v2.1 and above uses usernames (e.g. "nelson.jenkins" or "newusername") - NOT old-style names ("Nelson Jenkins" or "newusername Resident") and NOT display names ("Nelson the Magnificent" or "New User"). Separate values with commas (nelson.jenkins, newusername, etc.). Entries here are not case-sensitive.

==Updates & Release Notes==
You can update your IntelliDoor GSS by simply rezzing it.
* v2.1.3
** Fixed GSS not working with v2.1.1+ doors when ID has spaces.
* v2.1
** Changed old-style names to usernames.
** Slight tweaks.
* v2.0
** Primary public release.

==Builder Kit Instructions==
'''''ATTENTION USERS OF THE BUILDER KIT VERSIONS: THIS IS IMPORTANT, PLEASE READ''''' 
Your use of transfer-enabled products is bound by our [[Gentek Company Policy|Full Permissions Agreement]]. If you haven't read it, it's important you do so. 
Most importantly, we keep track of who has purchased the Builder Kit. If someone has a transferable IntelliDoor but has not bought the Builder Kit, that door will not function, and their use of it will be recorded. If you are found to be giving out transferable IntelliDoors, you will be backtraced by the cyber police, and consequences will never be the same. 
Therefore, ''make sure you set the door object to NO TRANSFER and the script inside it to NO TRANSFER before distributing it.'' However, '''leave the notecard FULL PERMISSIONS''' or it will break the script. Otherwise, you are risking both your license to use our products and your reputation with your customers, who will be left with prefabs that have their doors break when rezzed.

{{Gentek}}

@@ Line 27: / Line 27: @@
 ==Updates & Release Notes==
 You can update your IntelliDoor GSS by simply rezzing it.
 * v3.1.2
 ** Fixed GSS chaining issue in some cases

@@ Line 19: / Line 19: @@
 Multiple GSS units can now be chained together, such that there can be a "master" GSS, then other GSS units that pull from the "master". For example, the "master" GSS could hold administrator names for a building or region, then you could have a separate GSS for every area that would be managed by different people.<br>
 '''It is important that you do not create a loop with this feature!''' For example, if you chain two GSS units together, they will continuously "update" from each other, lagging down the communications channel. If you plan on using this feature, enable the "DEBUG=1" option. This will send you a message whenever the GSS data is downloaded or sent; if you notice that this keeps sending every so often, check to make sure you do not have a loop. You can set it back to "DEBUG=0" once you have checked this.
 ==Updates & Release Notes==
@@ Line 36: / Line 41: @@
 * v2.0
 ** Primary public release.
 {{Gentek}}

@@ Line 14: / Line 14: @@
 Because of LSL limitations, the whitelist line can only be read for 255 characters. However, the IntelliDoor system supports multiple whitelist lines. To be safe, separate your whitelist into 10-name increments, like so:<br>
 <code>WHITELIST=User01, User02, User03, User04, User05, User06, User07, User08, User09, User10<br>WHITELIST=User11, User12, User13, User14</code><br>
-You can have as many whitelist lines as you need.
+Due to more LSL limitations, the whitelist will max out at around 500 characters, or about 35 names. Chaining GSSes will not fix this.
 ==Chaining==

@@ Line 9: / Line 9: @@
 The GSS's primary purpose is its whitelist. When a door (or other component) "subscribes" to a GSS by using the same server name in its _config notecard, it loads this list upon resetting. As of v3.0, the blacklist was removed for compatibility purposes.<br>
 Those in the whitelist always have access to the door, regardless of the door's local settings. The lists are only limited by memory - theoretically, the system should handle more than 100 names easily.<br>
-NOTE ON NAMES: The IntelliDoor system v2.1 and above uses usernames (e.g. "nelson.jenkins" or "newusername") - NOT old-style names ("Nelson Jenkins" or "newusername Resident") and NOT display names ("Nelson the Magnificent" or "New User"). Separate values with commas (nelson.jenkins, newusername, etc.). Entries here are not case-sensitive.
+'''NOTE: Whitelist names are ''usernames'' (nelson.jenkins, newbie), not ''legacy names'' (Nelson Jenkins, Newbie Resident).''' If you have more than 10 names, please read "Extended Whitelist" below.
 ==Chaining==

@@ Line 3: / Line 3: @@
 ==Setup==
 # Rez the GSS object and open it by right clicking and selecting Open, then double-clicking the "_config" notecard.
-# Edit the notecard according to who you want to allow and disallow from all of the doors using this server. Make sure you change the server's name to the same server used by your doors. For more information on the whitelist and blacklist, read the section labeled "WHITELIST/BLACKLIST".
+# Edit the notecard according to who you want to allow and disallow from all of the doors using this server. Make sure you change the server's name to the same server used by your doors. For more information on the whitelist, read the section labeled "WHITELIST".
-# Save the notecard and close it. The server should automatically load the configuration.
+# Save the notecard and close it. The server should automatically load the configuration, and all doors using that GSS (v3.0 and above) should automatically reset.
-==Whitelist/Blacklist==
+==Whitelist==
-The GSS has two security features - a whitelist and a blacklist. When a door (or other component) "subscribes" to a GSS by using the same server name in its _config notecard, it loads these lists upon resetting.<br>
+The GSS's primary purpose is its whitelist. When a door (or other component) "subscribes" to a GSS by using the same server name in its _config notecard, it loads this list upon resetting. As of v3.0, the blacklist was removed for compatibility purposes.<br>
-Those in the whitelist always have access to the door, regardless of the door's local settings. Those in the blacklist will never have access to the door, even if it is unlocked or they have access through an Everyone or Group setting.<br>
+Those in the whitelist always have access to the door, regardless of the door's local settings. The lists are only limited by memory - theoretically, the system should handle more than 100 names easily.<br>
 NOTE ON NAMES: The IntelliDoor system v2.1 and above uses usernames (e.g. "nelson.jenkins" or "newusername") - NOT old-style names ("Nelson Jenkins" or "newusername Resident") and NOT display names ("Nelson the Magnificent" or "New User"). Separate values with commas (nelson.jenkins, newusername, etc.). Entries here are not case-sensitive.
 ==Updates & Release Notes==
 You can update your IntelliDoor GSS by simply rezzing it.
 * v2.1.3
 ** Fixed GSS not working with v2.1.1+ doors when ID has spaces.