Appboard/2.4/builder/system administration/session variables - Revision history

imported>Jason.nicholls: /* Managing Session Variables */

2014-08-04T17:47:24Z

Managing Session Variables

← Older revision		Revision as of 17:47, 4 August 2014
Line 61:		Line 61:
	** Encrypting a variable is a one-way operation: changing a variable marked as encrypted to unencrypted is not supported. Although the variable will still be functional, the strings will appear as encrypted values. The suggested alternatives are to either either delete the variable and re-create it, or re-enter the value in place of the encrypted string.		** Encrypting a variable is a one-way operation: changing a variable marked as encrypted to unencrypted is not supported. Although the variable will still be functional, the strings will appear as encrypted values. The suggested alternatives are to either either delete the variable and re-create it, or re-enter the value in place of the encrypted string.
	** Updating the encryption key with portal KeyCreate will require a full archive and restore to convert variable def default values and domain/user values. These are not updated on restart as for other parts of the system. The recommended approach is to do a KeyCreate before building up content (if needed).		** Updating the encryption key with portal KeyCreate will require a full archive and restore to convert variable def default values and domain/user values. These are not updated on restart as for other parts of the system. The recommended approach is to do a KeyCreate before building up content (if needed).
	* ''LDAP:'' this is hidden unless the ''User'' scope is checked. This setting is not currently supported or used. ~~You will need~~ to ~~follow~~ the ~~instructions in 'Pulling Extra User Context Variables from~~ LDAP~~' instead~~.		* ''LDAP:'' this is hidden unless the ''User'' scope is checked. This setting is not currently supported or used. Instead, for information on context variables from LDAP refer to the [[enportal/5.4/admin/user_administration/enPortal_LDAP_configuration#User_Context_Variables_from_LDAP\|LDAP Configuration]] documentation.
	\|-		\|-
	\|''Ordinal Position''		\|''Ordinal Position''

imported>Doug yeager: /* Managing Session Variables */

2014-06-23T20:24:15Z

Managing Session Variables

← Older revision		Revision as of 20:24, 23 June 2014
Line 61:		Line 61:
	** Encrypting a variable is a one-way operation: changing a variable marked as encrypted to unencrypted is not supported. Although the variable will still be functional, the strings will appear as encrypted values. The suggested alternatives are to either either delete the variable and re-create it, or re-enter the value in place of the encrypted string.		** Encrypting a variable is a one-way operation: changing a variable marked as encrypted to unencrypted is not supported. Although the variable will still be functional, the strings will appear as encrypted values. The suggested alternatives are to either either delete the variable and re-create it, or re-enter the value in place of the encrypted string.
	** Updating the encryption key with portal KeyCreate will require a full archive and restore to convert variable def default values and domain/user values. These are not updated on restart as for other parts of the system. The recommended approach is to do a KeyCreate before building up content (if needed).		** Updating the encryption key with portal KeyCreate will require a full archive and restore to convert variable def default values and domain/user values. These are not updated on restart as for other parts of the system. The recommended approach is to do a KeyCreate before building up content (if needed).
	* ''LDAP:'' this is hidden unless the ''User'' scope is checked. This setting is not currently used.		* ''LDAP:'' this is hidden unless the ''User'' scope is checked. This setting is not currently supported or used. You will need to follow the instructions in 'Pulling Extra User Context Variables from LDAP' instead.
	\|-		\|-
	\|''Ordinal Position''		\|''Ordinal Position''

imported>Andy.hopper: /* Managing Session Variables */

2014-06-04T19:28:13Z

Managing Session Variables

← Older revision		Revision as of 19:28, 4 June 2014
Line 61:		Line 61:
	** Encrypting a variable is a one-way operation: changing a variable marked as encrypted to unencrypted is not supported. Although the variable will still be functional, the strings will appear as encrypted values. The suggested alternatives are to either either delete the variable and re-create it, or re-enter the value in place of the encrypted string.		** Encrypting a variable is a one-way operation: changing a variable marked as encrypted to unencrypted is not supported. Although the variable will still be functional, the strings will appear as encrypted values. The suggested alternatives are to either either delete the variable and re-create it, or re-enter the value in place of the encrypted string.
	** Updating the encryption key with portal KeyCreate will require a full archive and restore to convert variable def default values and domain/user values. These are not updated on restart as for other parts of the system. The recommended approach is to do a KeyCreate before building up content (if needed).		** Updating the encryption key with portal KeyCreate will require a full archive and restore to convert variable def default values and domain/user values. These are not updated on restart as for other parts of the system. The recommended approach is to do a KeyCreate before building up content (if needed).
	* ''LDAP:'' this is hidden unless the ''User'' scope is checked. This is ~~an '''indicator only''' for the administrator that this variable will be set dynamically from LDAP~~. ~~LDAP-to-variable mappings are specified in ''custom.properties'' and take the form:~~		* ''LDAP:'' this is hidden unless the ''User'' scope is checked. This setting is not currently used.
	*:<tt>ldap.userInfo.<variable></tt><br>
	*:For instance, the following would specify that ''phone'' and ''mhvalue'' will be retrieved from LDAP on defined users:
	*:<tt>ldap.userInfo.phone<BR>ldap.userInfo.mhvalue</tt>
	\|-		\|-
	\|''Ordinal Position''		\|''Ordinal Position''

imported>Andy.hopper: /* Managing Session Variables */

2014-05-28T14:00:34Z

Managing Session Variables

← Older revision		Revision as of 14:00, 28 May 2014
Line 62:		Line 62:
	** Updating the encryption key with portal KeyCreate will require a full archive and restore to convert variable def default values and domain/user values. These are not updated on restart as for other parts of the system. The recommended approach is to do a KeyCreate before building up content (if needed).		** Updating the encryption key with portal KeyCreate will require a full archive and restore to convert variable def default values and domain/user values. These are not updated on restart as for other parts of the system. The recommended approach is to do a KeyCreate before building up content (if needed).
	* ''LDAP:'' this is hidden unless the ''User'' scope is checked. This is an '''indicator only''' for the administrator that this variable will be set dynamically from LDAP. LDAP-to-variable mappings are specified in ''custom.properties'' and take the form:		* ''LDAP:'' this is hidden unless the ''User'' scope is checked. This is an '''indicator only''' for the administrator that this variable will be set dynamically from LDAP. LDAP-to-variable mappings are specified in ''custom.properties'' and take the form:
	<tt>ldap.userInfo.<variable></tt><br>		*:<tt>ldap.userInfo.<variable></tt><br>
	For instance, the following would specify that ''phone'' and ''mhvalue'' will be retrieved from LDAP on defined users:~~<br>~~		*:For instance, the following would specify that ''phone'' and ''mhvalue'' will be retrieved from LDAP on defined users:
	<tt>		*:<tt>ldap.userInfo.phone<BR>ldap.userInfo.mhvalue</tt>
	ldap.userInfo.phone<br>
	ldap.userInfo.mhvalue
	</tt>
	\|-		\|-
	\|''Ordinal Position''		\|''Ordinal Position''

imported>Andy.hopper: /* Managing Session Variables */

2014-05-28T13:58:42Z

Managing Session Variables

← Older revision		Revision as of 13:58, 28 May 2014
Line 61:		Line 61:
	** Encrypting a variable is a one-way operation: changing a variable marked as encrypted to unencrypted is not supported. Although the variable will still be functional, the strings will appear as encrypted values. The suggested alternatives are to either either delete the variable and re-create it, or re-enter the value in place of the encrypted string.		** Encrypting a variable is a one-way operation: changing a variable marked as encrypted to unencrypted is not supported. Although the variable will still be functional, the strings will appear as encrypted values. The suggested alternatives are to either either delete the variable and re-create it, or re-enter the value in place of the encrypted string.
	** Updating the encryption key with portal KeyCreate will require a full archive and restore to convert variable def default values and domain/user values. These are not updated on restart as for other parts of the system. The recommended approach is to do a KeyCreate before building up content (if needed).		** Updating the encryption key with portal KeyCreate will require a full archive and restore to convert variable def default values and domain/user values. These are not updated on restart as for other parts of the system. The recommended approach is to do a KeyCreate before building up content (if needed).
	* ''LDAP:'' this is hidden unless the ''User'' scope is checked. This is an '''indicator only''' for the administrator that this variable will be set dynamically from LDAP. LDAP-to-variable mappings are specified in ~~a configuration file (please contact support)~~.		* ''LDAP:'' this is hidden unless the ''User'' scope is checked. This is an '''indicator only''' for the administrator that this variable will be set dynamically from LDAP. LDAP-to-variable mappings are specified in ''custom.properties'' and take the form:
			<tt>ldap.userInfo.<variable></tt><br>
			For instance, the following would specify that ''phone'' and ''mhvalue'' will be retrieved from LDAP on defined users:<br>
			<tt>
			ldap.userInfo.phone<br>
			ldap.userInfo.mhvalue
			</tt>
	\|-		\|-
	\|''Ordinal Position''		\|''Ordinal Position''

imported>Andy.hopper: /* Managing Session Variables */

2014-04-02T19:27:55Z

Managing Session Variables

← Older revision		Revision as of 19:27, 2 April 2014
Line 61:		Line 61:
	** Encrypting a variable is a one-way operation: changing a variable marked as encrypted to unencrypted is not supported. Although the variable will still be functional, the strings will appear as encrypted values. The suggested alternatives are to either either delete the variable and re-create it, or re-enter the value in place of the encrypted string.		** Encrypting a variable is a one-way operation: changing a variable marked as encrypted to unencrypted is not supported. Although the variable will still be functional, the strings will appear as encrypted values. The suggested alternatives are to either either delete the variable and re-create it, or re-enter the value in place of the encrypted string.
	** Updating the encryption key with portal KeyCreate will require a full archive and restore to convert variable def default values and domain/user values. These are not updated on restart as for other parts of the system. The recommended approach is to do a KeyCreate before building up content (if needed).		** Updating the encryption key with portal KeyCreate will require a full archive and restore to convert variable def default values and domain/user values. These are not updated on restart as for other parts of the system. The recommended approach is to do a KeyCreate before building up content (if needed).
	* ''LDAP:'' this is hidden unless the ''User'' scope is checked. This is an '''indicator only''' for the administrator that this variable will be set dynamically from LDAP. ~~The job of configuring~~ LDAP-to-variable ~~mapping is via~~ configuration file (please contact support).		* ''LDAP:'' this is hidden unless the ''User'' scope is checked. This is an '''indicator only''' for the administrator that this variable will be set dynamically from LDAP. LDAP-to-variable mappings are specified in a configuration file (please contact support).
	\|-		\|-
	\|''Ordinal Position''		\|''Ordinal Position''

imported>Andy.hopper: /* Managing Session Variables */

2014-04-02T19:25:35Z

Managing Session Variables

← Older revision		Revision as of 19:25, 2 April 2014
Line 59:		Line 59:
	* ''Server Use Only:'' on by default and means the variable cannot be modified by the client, with the exception of the administrator via the Builder. Disabling this option means the client can override this variable via URL parameters - see the [[appboard/2.4/admin/accessing_appboard#Session Variables\|Accessing AppBoard]] page for more information.		* ''Server Use Only:'' on by default and means the variable cannot be modified by the client, with the exception of the administrator via the Builder. Disabling this option means the client can override this variable via URL parameters - see the [[appboard/2.4/admin/accessing_appboard#Session Variables\|Accessing AppBoard]] page for more information.
	* ''Encrypted:'' This flag will ensure the variable value is not displayed to the user in any context (instead, it will be displayed as repeated asterisks). ''Please note that the following caveats should be considered regarding encrypted variables:''		* ''Encrypted:'' This flag will ensure the variable value is not displayed to the user in any context (instead, it will be displayed as repeated asterisks). ''Please note that the following caveats should be considered regarding encrypted variables:''
	** Encrypting a variable is a one-way operation: changing a variable marked as encrypted to unencrypted is not supported. Although the variable will still be functional, the strings will appear as encrypted values ~~since they are not decrypted~~. The suggested alternatives are to either either delete the variable and re-create it, or re-enter the value in place of the encrypted string.		** Encrypting a variable is a one-way operation: changing a variable marked as encrypted to unencrypted is not supported. Although the variable will still be functional, the strings will appear as encrypted values. The suggested alternatives are to either either delete the variable and re-create it, or re-enter the value in place of the encrypted string.
	** Updating the encryption key with portal KeyCreate will require a full archive and restore to convert variable def default values and domain/user values. These are not updated on restart as for other parts of the system. The recommended approach is to do a KeyCreate before building up content (if needed).		** Updating the encryption key with portal KeyCreate will require a full archive and restore to convert variable def default values and domain/user values. These are not updated on restart as for other parts of the system. The recommended approach is to do a KeyCreate before building up content (if needed).
	* ''LDAP:'' this is hidden unless the ''User'' scope is checked. This is an '''indicator only''' for the administrator that this variable will be set dynamically from LDAP. The job of configuring LDAP-to-variable mapping is via configuration file (please contact support).		* ''LDAP:'' this is hidden unless the ''User'' scope is checked. This is an '''indicator only''' for the administrator that this variable will be set dynamically from LDAP. The job of configuring LDAP-to-variable mapping is via configuration file (please contact support).

imported>Andy.hopper: /* Managing Session Variables */

2014-04-02T19:24:42Z

Managing Session Variables

← Older revision		Revision as of 19:24, 2 April 2014
Line 58:		Line 58:
	\|		\|
	* ''Server Use Only:'' on by default and means the variable cannot be modified by the client, with the exception of the administrator via the Builder. Disabling this option means the client can override this variable via URL parameters - see the [[appboard/2.4/admin/accessing_appboard#Session Variables\|Accessing AppBoard]] page for more information.		* ''Server Use Only:'' on by default and means the variable cannot be modified by the client, with the exception of the administrator via the Builder. Disabling this option means the client can override this variable via URL parameters - see the [[appboard/2.4/admin/accessing_appboard#Session Variables\|Accessing AppBoard]] page for more information.
	* ''Encrypted:'' This flag will ensure the variable value is not displayed to the user in any context (instead, it will be displayed as repeated asterisks).		* ''Encrypted:'' This flag will ensure the variable value is not displayed to the user in any context (instead, it will be displayed as repeated asterisks). ''Please note that the following caveats should be considered regarding encrypted variables:''
			** Encrypting a variable is a one-way operation: changing a variable marked as encrypted to unencrypted is not supported. Although the variable will still be functional, the strings will appear as encrypted values since they are not decrypted. The suggested alternatives are to either either delete the variable and re-create it, or re-enter the value in place of the encrypted string.
			** Updating the encryption key with portal KeyCreate will require a full archive and restore to convert variable def default values and domain/user values. These are not updated on restart as for other parts of the system. The recommended approach is to do a KeyCreate before building up content (if needed).
	* ''LDAP:'' this is hidden unless the ''User'' scope is checked. This is an '''indicator only''' for the administrator that this variable will be set dynamically from LDAP. The job of configuring LDAP-to-variable mapping is via configuration file (please contact support).		* ''LDAP:'' this is hidden unless the ''User'' scope is checked. This is an '''indicator only''' for the administrator that this variable will be set dynamically from LDAP. The job of configuring LDAP-to-variable mapping is via configuration file (please contact support).
	\|-		\|-

imported>Andy.hopper: /* Managing Session Variables */

2014-04-02T19:16:35Z

Managing Session Variables

← Older revision		Revision as of 19:16, 2 April 2014
Line 58:		Line 58:
	\|		\|
	* ''Server Use Only:'' on by default and means the variable cannot be modified by the client, with the exception of the administrator via the Builder. Disabling this option means the client can override this variable via URL parameters - see the [[appboard/2.4/admin/accessing_appboard#Session Variables\|Accessing AppBoard]] page for more information.		* ''Server Use Only:'' on by default and means the variable cannot be modified by the client, with the exception of the administrator via the Builder. Disabling this option means the client can override this variable via URL parameters - see the [[appboard/2.4/admin/accessing_appboard#Session Variables\|Accessing AppBoard]] page for more information.
	* ''Encrypted:'' This flag will ensure the variable value is not ~~shown anywhere~~ in ~~the AppBoard UI~~, ~~instead the string <tt>!!encrypted!!</tt> is shown~~.		* ''Encrypted:'' This flag will ensure the variable value is not displayed to the user in any context (instead, it will be displayed as repeated asterisks).
	* ''LDAP:'' this is hidden unless the ''User'' scope is checked. This is an '''indicator only''' for the administrator that this variable will be set dynamically from LDAP. The job of configuring LDAP-to-variable mapping is via configuration file (please contact support).		* ''LDAP:'' this is hidden unless the ''User'' scope is checked. This is an '''indicator only''' for the administrator that this variable will be set dynamically from LDAP. The job of configuring LDAP-to-variable mapping is via configuration file (please contact support).
	\|-		\|-

imported>Jason.nicholls at 07:16, 14 December 2013

2013-12-14T07:16:57Z

← Older revision		Revision as of 07:16, 14 December 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:Session Variables}}		{{DISPLAYTITLE:Session Variables}}
			[[Category:AppBoard 2.4]]
	The Session Variable administration page allows the definition and default configuration for session variables within the AppBoard system.		The Session Variable administration page allows the definition and default configuration for session variables within the AppBoard system.