Appboard/2.4/admin/provisioning - Revision history

imported>Jason.nicholls: /* Managing Provisioning */

2014-07-16T14:43:43Z

Managing Provisioning

← Older revision		Revision as of 14:43, 16 July 2014
Line 91:		Line 91:
	* [[appboard/2.4/builder/system_administration#Provisioning\|Manual management via Builder]]: This includes configuring LDAP managed Domains and LDAP role mapping.		* [[appboard/2.4/builder/system_administration#Provisioning\|Manual management via Builder]]: This includes configuring LDAP managed Domains and LDAP role mapping.
	* [[appboard/2.4/admin/provisioning/batch_loading\|Batch loading via XML]]: Loading domains, users, roles, and role assignments in bulk via XML files.		* [[appboard/2.4/admin/provisioning/batch_loading\|Batch loading via XML]]: Loading domains, users, roles, and role assignments in bulk via XML files.
	* [[~~Direct_Provisioning~~\|Custom JSP]]: ~~i.e.~~ build a custom web service for provisioning.		* [[appboard/2.4/admin/provisioning/custom_jsp\|Custom JSP]]: build a custom web service for provisioning.

imported>Jason.nicholls: /* Managing Provisioning */

2014-07-16T09:29:17Z

Managing Provisioning

← Older revision		Revision as of 09:29, 16 July 2014
Line 90:		Line 90:

	* [[appboard/2.4/builder/system_administration#Provisioning\|Manual management via Builder]]: This includes configuring LDAP managed Domains and LDAP role mapping.		* [[appboard/2.4/builder/system_administration#Provisioning\|Manual management via Builder]]: This includes configuring LDAP managed Domains and LDAP role mapping.
	* [[appboard/2.4/admin/provisioning/batch_loading\|Batch loading via XML]]		* [[appboard/2.4/admin/provisioning/batch_loading\|Batch loading via XML]]: Loading domains, users, roles, and role assignments in bulk via XML files.
	* [[Direct_Provisioning\|Custom JSP]]: i.e. build a custom web service for provisioning.		* [[Direct_Provisioning\|Custom JSP]]: i.e. build a custom web service for provisioning.

imported>Jason.nicholls: /* Managing Provisioning */

2014-07-16T08:21:26Z

Managing Provisioning

← Older revision		Revision as of 08:21, 16 July 2014
Line 90:		Line 90:

	* [[appboard/2.4/builder/system_administration#Provisioning\|Manual management via Builder]]: This includes configuring LDAP managed Domains and LDAP role mapping.		* [[appboard/2.4/builder/system_administration#Provisioning\|Manual management via Builder]]: This includes configuring LDAP managed Domains and LDAP role mapping.
	* [[~~Batch_Loading_Users~~\|Batch loading via XML]]		* [[appboard/2.4/admin/provisioning/batch_loading\|Batch loading via XML]]
	* [[Direct_Provisioning\|Custom JSP]]: i.e. build a custom web service for provisioning.		* [[Direct_Provisioning\|Custom JSP]]: i.e. build a custom web service for provisioning.

imported>Jason.nicholls: moved appboard/2.4/admin/provisioning/overview to appboard/2.4/admin/provisioning

2014-07-16T07:56:42Z

moved appboard/2.4/admin/provisioning/overview to appboard/2.4/admin/provisioning

← Older revision	Revision as of 07:56, 16 July 2014
(No difference)

imported>Jason.nicholls at 07:53, 16 July 2014

2014-07-16T07:53:30Z

← Older revision		Revision as of 07:53, 16 July 2014
Line 5:		Line 5:
	For a User to log in to AppBoard and view content, an Administrator must first create the User in the system and then assign appropriate content to that User. Provisioning is the means of configuring these users, domains, roles, content, and assignments between users and roles, and content and roles.		For a User to log in to AppBoard and view content, an Administrator must first create the User in the system and then assign appropriate content to that User. Provisioning is the means of configuring these users, domains, roles, content, and assignments between users and roles, and content and roles.

	AppBoard and enPortal share much of the same provisioning model under the covers but actual assignment of content to roles differs. If planning to use enPortal proxied content with AppBoard dashboards then also read over the [[enportal/5.4/admin/user_administration\|enPortal User Administration]] documentation.		AppBoard and enPortal share much of the same provisioning model under the covers but actual assignment of content to roles differs. Within AppBoard content is assigned by ''Stacks'' to roles, and roles assigned to users and domains.

			If planning to use enPortal proxied content with AppBoard dashboards then also read over the [[enportal/5.4/admin/user_administration\|enPortal User Administration]] documentation.

	== Domains & Users ==		== Domains & Users ==
Line 82:		Line 84:

	For information on including enPortal proxied content into AppBoard dashboards, refer to the [[appboard/2.4/builder/widgets/web_page\|Web Page Widget]] documentation.		For information on including enPortal proxied content into AppBoard dashboards, refer to the [[appboard/2.4/builder/widgets/web_page\|Web Page Widget]] documentation.

			= Managing Provisioning =

			Managing domains, users, roles, and how stacks are assigned to roles is managed manually via the Builder interface or handled via XML interface or custom JSP interface for automated and bulk-loading applications.

			* [[appboard/2.4/builder/system_administration#Provisioning\|Manual management via Builder]]: This includes configuring LDAP managed Domains and LDAP role mapping.
			* [[Batch_Loading_Users\|Batch loading via XML]]
			* [[Direct_Provisioning\|Custom JSP]]: i.e. build a custom web service for provisioning.

imported>Jason.nicholls: /* Stack Assignment */

2014-07-16T07:49:21Z

Stack Assignment

← Older revision		Revision as of 07:49, 16 July 2014
Line 68:		Line 68:

	== Stack Assignment ==		== Stack Assignment ==

			Stack assignment is about provisioning content, in the form of one or more Stacks, to a particular role. In AppBoard this is a simple drag-and-drop process. The ordering of the Stacks determines the order the Stacks will be visible in the AppBoard ''Viewer''.

	Refer to the [[appboard/2.4/builder/system_administration\|System Administation]] documentation for managing Stack Assignment within AppBoard.		Refer to the [[appboard/2.4/builder/system_administration\|System Administation]] documentation for managing Stack Assignment within AppBoard.

imported>Jason.nicholls at 07:47, 16 July 2014

2014-07-16T07:47:00Z

← Older revision		Revision as of 07:47, 16 July 2014
Line 9:		Line 9:
	== Domains & Users ==		== Domains & Users ==

	== Domains ==		=== Domains ===

	All ''Users'' in AppBoard belong to a ''Domain''. It's the combination of user + domain that identifies a unique user to the system. This also implies that within a domain the user name must be unique.		All ''Users'' in AppBoard belong to a ''Domain''. It's the combination of user + domain that identifies a unique user to the system. This also implies that within a domain the user name must be unique.
Line 32:		Line 32:
	Refer to the [[appboard/2.4/builder/system_administration\|System Administation]] documentation for managing Domains within AppBoard.		Refer to the [[appboard/2.4/builder/system_administration\|System Administation]] documentation for managing Domains within AppBoard.

	== Users ==		=== Users ===

	As mentioned above, a combination of user + domain identifies a unique user to the AppBoard system. Authentication for all users of the domain depends on the domain, either internally or via external authentication such as with LDAP-based systems.		As mentioned above, a combination of user + domain identifies a unique user to the AppBoard system. Authentication for all users of the domain depends on the domain, either internally or via external authentication such as with LDAP-based systems.
Line 43:		Line 43:
	* Role Assignment. Assignment of roles to a user is in addition to any roles assigned at the domain level.		* Role Assignment. Assignment of roles to a user is in addition to any roles assigned at the domain level.
	* User scoped Session Variables.		* User scoped Session Variables.
	* (enPortal) SSO Assignment. Assigning SSO tokens at the user level can be done explicitly by the administrator or when prompted by the system and a user enters their application credentials. ~~If a token matches the same target as a token assigned at the domain level, then the user~~ level ~~token~~ takes precedence.		* (enPortal) SSO Assignment. Assigning SSO tokens at the user level can be done explicitly by the administrator or when prompted by the system and a user enters their application credentials. User level tokens always takes precedence over domain-assigned, or role-assigned tokens.

	Refer to the [[appboard/2.4/builder/system_administration\|System Administation]] documentation for managing Users within AppBoard.		Refer to the [[appboard/2.4/builder/system_administration\|System Administation]] documentation for managing Users within AppBoard.
Line 50:		Line 50:

	== Roles ==		== Roles ==

			In AppBoard roles are primarily a grouping mechanism for assigning content. Content is assigned to the roles, and roles are assigned to domains and users.

			Multiple roles can be assigned to a user, either directly or inherited through assignment to the user's domain. However, when a user logs into the system they only assume a single role. This is shown in the application header and a drop-down provided if the user has access to multiple roles. Switching roles will change what content is visible to the user.

			As Roles can be managed internally but also externally with LDAP-based role adapters, or with custom integrations.

			Role naming internal to AppBoard is actually stored as path, for example <tt>/portalAdministration</tt>, <tt>/cat</tt> and <tt>/cat/dog</tt>, however '''no inheritance is implied'''. Each role is unique and only provides access to the content directly assigned to it. Typically this is only evident when using LDAP-based role adapters where the role adapter name forms part of the path, such as <tt>/my_LDAP_role_adapter/roleA</tt>.

			Overall roles are used for:

			* Content Assignment. One or more stacks are assigned to the role.
			* (enPortal) Content Assignment. One or more folders and channels assigned.
			* (enPortal) SSO Assignment. Similar to domain-assigned SSO tokens, these apply to a user if the role is assigned and the user is assuming that role.

	Refer to the [[appboard/2.4/builder/system_administration\|System Administation]] documentation for managing Roles within AppBoard.		Refer to the [[appboard/2.4/builder/system_administration\|System Administation]] documentation for managing Roles within AppBoard.

imported>Jason.nicholls at 06:26, 16 July 2014

2014-07-16T06:26:13Z

@@ Line 7: / Line 7: @@
 AppBoard and enPortal share much of the same provisioning model under the covers but actual assignment of content to roles differs. If planning to use enPortal proxied content with AppBoard dashboards then also read over the [[enportal/5.4/admin/user_administration|enPortal User Administration]] documentation.
-== Domains and Users ==
+== Domains & Users ==
 == Domains ==
@@ Line 30: / Line 30: @@
 * (enPortal) LAF Assignment. With enPortal each domain can be assigned a different look-and-feel to the system-wide default.
 == Users ==
@@ Line 44: / Line 45: @@
 * (enPortal) SSO Assignment. Assigning SSO tokens at the user level can be done explicitly by the administrator or when prompted by the system and a user enters their application credentials. If a token matches the same target as a token assigned at the domain level, then the user level token takes precedence.
-= Roles =
+Refer to the [[appboard/2.4/builder/system_administration|System Administation]] documentation for managing Users within AppBoard.
-[[Image:Domain_Illustration.png|thumb|center|300px|Domains and Users Example]]
+= Roles & Stack Assignment =
-As a first step in determining your User organization, determine if separate Domains need to be created so that users from one Domain would access the system independently from users in the other Domain.  For example, a managed service provider may want to group customers into separate Domains if they will be completely independent from one another in how they use the system.
+Refer to the [[appboard/2.4/builder/system_administration|System Administation]] documentation for managing Roles within AppBoard.
-After creating each Domain, you will then assign one or more Roles to each Domain.  These Roles will dictate the system content that is available to Users in that Domain.  When a Role is assigned to a Domain, then all Users belonging to that Domain inherit the Role.  New Users added later to the Domain would then automatically inherit these assignments.
+Refer to the [[appboard/2.4/builder/system_administration|System Administation]] documentation for managing Stack Assignment within AppBoard.
-=== Roles ===
+= Creating Content =
-Roles are a hierarchical mechanism used to organize Domains and Users. Roles are the primary basis by which
+Creating content in AppBoard is through using the ''Builder'' and adding top-level Boards (Stacks), drill-down Boards, and widgets for these Boards.
-[[Image:RoleHierarchy.png|thumb|center|300px|Role Hierarchy Example]]
+For more information on building content refer to the [[appboard/2.4/builder|AppBoard Builder]] documentation.
+For information on including enPortal proxied content into AppBoard dashboards, refer to the [[appboard/2.4/builder/widgets/web_page|Web Page Widget]] documentation.

imported>Jason.nicholls at 06:17, 16 July 2014

2014-07-16T06:17:03Z

← Older revision		Revision as of 06:17, 16 July 2014
Line 26:		Line 26:
	* Password Policies. Enforce a policy on users within this group. Please note this may not apply if using external authentication.		* Password Policies. Enforce a policy on users within this group. Please note this may not apply if using external authentication.
	* Role Assignment. Assignment of roles to a domain means that all users within the domain have that role.		* Role Assignment. Assignment of roles to a domain means that all users within the domain have that role.
			* Domain scoped Session Variables.
	* (enPortal) SSO Assignment. Assignment of single sign-on (SSO) tokens at the domain means that all users within the domain will use those SSO credentials for the specified targeted proxied applications.		* (enPortal) SSO Assignment. Assignment of single sign-on (SSO) tokens at the domain means that all users within the domain will use those SSO credentials for the specified targeted proxied applications.
	* (enPortal) LAF Assignment. With enPortal each domain can be assigned a different look-and-feel to the system-wide default.		* (enPortal) LAF Assignment. With enPortal each domain can be assigned a different look-and-feel to the system-wide default.
Line 34:		Line 35:
	As mentioned above, a combination of user + domain identifies a unique user to the AppBoard system. Authentication for all users of the domain depends on the domain, either internally or via external authentication such as with LDAP-based systems.		As mentioned above, a combination of user + domain identifies a unique user to the AppBoard system. Authentication for all users of the domain depends on the domain, either internally or via external authentication such as with LDAP-based systems.

			When a user is logged into AppBoard they must have at least one role assigned, and content assigned to that role, in order to access the system. If multiple roles are assigned then the user can choose which role they want to be via a drop-down in the application header. See the Roles section below for more information.

			The following assignments and configuration are available at the user level:

			* Account Lock: administrator is able to lock/unlock specific accounts
			* Role Assignment. Assignment of roles to a user is in addition to any roles assigned at the domain level.
			* User scoped Session Variables.
			* (enPortal) SSO Assignment. Assigning SSO tokens at the user level can be done explicitly by the administrator or when prompted by the system and a user enters their application credentials. If a token matches the same target as a token assigned at the domain level, then the user level token takes precedence.

			= Roles =

	[[Image:Domain_Illustration.png\|thumb\|center\|300px\|Domains and Users Example]]		[[Image:Domain_Illustration.png\|thumb\|center\|300px\|Domains and Users Example]]

imported>Jason.nicholls: /* Users */

2014-07-16T06:11:05Z

Users

← Older revision		Revision as of 06:11, 16 July 2014
Line 31:		Line 31:

	== Users ==		== Users ==

			As mentioned above, a combination of user + domain identifies a unique user to the AppBoard system. Authentication for all users of the domain depends on the domain, either internally or via external authentication such as with LDAP-based systems.

← Older revision		Revision as of 14:43, 16 July 2014
Line 91:		Line 91:
	* [[appboard/2.4/builder/system_administration#Provisioning\|Manual management via Builder]]: This includes configuring LDAP managed Domains and LDAP role mapping.		* [[appboard/2.4/builder/system_administration#Provisioning\|Manual management via Builder]]: This includes configuring LDAP managed Domains and LDAP role mapping.
	* [[appboard/2.4/admin/provisioning/batch_loading\|Batch loading via XML]]: Loading domains, users, roles, and role assignments in bulk via XML files.		* [[appboard/2.4/admin/provisioning/batch_loading\|Batch loading via XML]]: Loading domains, users, roles, and role assignments in bulk via XML files.
	* [[~~Direct_Provisioning~~\|Custom JSP]]: ~~i.e.~~ build a custom web service for provisioning.		* [[appboard/2.4/admin/provisioning/custom_jsp\|Custom JSP]]: build a custom web service for provisioning.

← Older revision		Revision as of 09:29, 16 July 2014
Line 90:		Line 90:

	* [[appboard/2.4/builder/system_administration#Provisioning\|Manual management via Builder]]: This includes configuring LDAP managed Domains and LDAP role mapping.		* [[appboard/2.4/builder/system_administration#Provisioning\|Manual management via Builder]]: This includes configuring LDAP managed Domains and LDAP role mapping.
	* [[appboard/2.4/admin/provisioning/batch_loading\|Batch loading via XML]]		* [[appboard/2.4/admin/provisioning/batch_loading\|Batch loading via XML]]: Loading domains, users, roles, and role assignments in bulk via XML files.
	* [[Direct_Provisioning\|Custom JSP]]: i.e. build a custom web service for provisioning.		* [[Direct_Provisioning\|Custom JSP]]: i.e. build a custom web service for provisioning.

← Older revision		Revision as of 08:21, 16 July 2014
Line 90:		Line 90:

	* [[appboard/2.4/builder/system_administration#Provisioning\|Manual management via Builder]]: This includes configuring LDAP managed Domains and LDAP role mapping.		* [[appboard/2.4/builder/system_administration#Provisioning\|Manual management via Builder]]: This includes configuring LDAP managed Domains and LDAP role mapping.
	* [[~~Batch_Loading_Users~~\|Batch loading via XML]]		* [[appboard/2.4/admin/provisioning/batch_loading\|Batch loading via XML]]
	* [[Direct_Provisioning\|Custom JSP]]: i.e. build a custom web service for provisioning.		* [[Direct_Provisioning\|Custom JSP]]: i.e. build a custom web service for provisioning.