Enportal/5.5/admin/user administration/sso - Revision history

imported>Jason.nicholls: /* Overview */

2014-10-27T07:44:07Z

Overview

← Older revision		Revision as of 07:44, 27 October 2014
Line 5:		Line 5:
	Single-Sign-On (SSO) and Sign-Off provides a convenient way for users to sign in once to enPortal and have enPortal manage sign-on credentials for proxied web applications. enPortal can then automatically sign-on on behalf of a user when they first access the proxied web content, and automatically sign-off once they log out of enPortal.		Single-Sign-On (SSO) and Sign-Off provides a convenient way for users to sign in once to enPortal and have enPortal manage sign-on credentials for proxied web applications. enPortal can then automatically sign-on on behalf of a user when they first access the proxied web content, and automatically sign-off once they log out of enPortal.

	[[File:enportal-5.5-sso-diagram.png\|~~frame~~\|center\|enPortal manages signing on to proxied applications on behalf of the user.]]		[[File:enportal-5.5-sso-diagram.png\|thumb\|500px\|center\|enPortal manages signing on to proxied applications on behalf of the user.]]

	=== SSO Authentication Types ===		=== SSO Authentication Types ===

imported>Jason.nicholls: /* Overview */

2014-10-27T07:43:08Z

Overview

← Older revision		Revision as of 07:43, 27 October 2014
Line 4:		Line 4:

	Single-Sign-On (SSO) and Sign-Off provides a convenient way for users to sign in once to enPortal and have enPortal manage sign-on credentials for proxied web applications. enPortal can then automatically sign-on on behalf of a user when they first access the proxied web content, and automatically sign-off once they log out of enPortal.		Single-Sign-On (SSO) and Sign-Off provides a convenient way for users to sign in once to enPortal and have enPortal manage sign-on credentials for proxied web applications. enPortal can then automatically sign-on on behalf of a user when they first access the proxied web content, and automatically sign-off once they log out of enPortal.

			[[File:enportal-5.5-sso-diagram.png\|frame\|center\|enPortal manages signing on to proxied applications on behalf of the user.]]

	=== SSO Authentication Types ===		=== SSO Authentication Types ===

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

2014-10-27T07:42:03Z

SSO Assignment

← Older revision		Revision as of 07:42, 27 October 2014
Line 17:		Line 17:
	SSO tokens can also be assigned at different levels:		SSO tokens can also be assigned at different levels:

	* ''not assigned'': when a user first accesses proxied content that requires authentication the user is prompted to enter access credentials. These are then saved against the specific user.		* ''not assigned'': when a user first accesses proxied content that requires authentication, and no existing token is applicable, the user is prompted to enter access credentials. These are then saved against the specific user.
	* User: Administrators can create tokens and assign to specific users.		* User: Administrators can create tokens and assign to specific users. These tokens are the most specific and take precedence over Role or Domain-level tokens.
	* Domain: Administrators can create tokens and assign to a Domain, these tokens are ~~then used for all users within~~ the ~~domain. If a user also has user-level tokens then those will~~ take precedence over ~~a domain~~-level ~~token~~.		* Role: Administrators can create tokens and assign to a Role, these tokens are then used whenever a user is logged in using that role. Role-level tokens take precedence over Domain-level tokens.
	* Role: Administrators can create tokens and assign to a Role, these tokens are then used whenever a user is logged in using that role. ~~If a user also has user~~-level tokens ~~then those will~~ take precedence over ~~role~~-level tokens.		* Domain: Administrators can create tokens and assign to a Domain, these tokens are then used for all users within the domain.

	=== Stored & Pass-through Credentials ===		=== Stored & Pass-through Credentials ===

imported>Jason.nicholls: /* SSO Settings */

2014-10-24T09:04:36Z

SSO Settings

← Older revision		Revision as of 09:04, 24 October 2014
Line 45:		Line 45:
	When adding or editing an SSO token there are two main groups of settings:		When adding or editing an SSO token there are two main groups of settings:

	# The ''Auth Name'', which defines the authentication type and is not editable. And the target application ''Host Name / IP'' and ''Port''.		# The ''Auth Name'', which defines the authentication type and is not editable. And the target application ''Host Name / IP'' and ''Port''. These fields are used so enPortal can determine when to use this particular authentication token.
	# The authentication credentials. Typically this is ''username'' and ''password'', but depending on the authentication type there may be different or additional fields. For example, in the screenshot below for NTLM authentication there is an optional ''~~Domain~~'' field.		# The authentication credentials. Typically this is ''username'' and ''password'', but depending on the authentication type there may be different or additional fields. For example, in the screenshot below for NTLM authentication there is an optional ''domain'' field.

	[[File:enportal-5.5-sso-ntlm.png\|frame\|center\|NTLM SSO token settings, notice additional Domain field.]]		[[File:enportal-5.5-sso-ntlm.png\|frame\|center\|NTLM SSO token settings, notice additional Domain field.]]

imported>Jason.nicholls: /* SSO Settings */

2014-10-24T09:03:21Z

SSO Settings

← Older revision		Revision as of 09:03, 24 October 2014
Line 46:		Line 46:

	# The ''Auth Name'', which defines the authentication type and is not editable. And the target application ''Host Name / IP'' and ''Port''.		# The ''Auth Name'', which defines the authentication type and is not editable. And the target application ''Host Name / IP'' and ''Port''.
	# The authentication credentials. Typically this is ''username'' and 'password'', but depending on the authentication type there may be different or additional fields. For example, in the screenshot below for NTLM authentication there is an optional ''Domain'' field.		# The authentication credentials. Typically this is ''username'' and ''password'', but depending on the authentication type there may be different or additional fields. For example, in the screenshot below for NTLM authentication there is an optional ''Domain'' field.

	[[File:enportal-5.5-sso-ntlm.png\|frame\|center\|NTLM SSO token settings, notice additional Domain field.]]		[[File:enportal-5.5-sso-ntlm.png\|frame\|center\|NTLM SSO token settings, notice additional Domain field.]]

imported>Jason.nicholls: /* SSO Settings */

2014-10-24T08:58:30Z

SSO Settings

← Older revision		Revision as of 08:58, 24 October 2014
Line 45:		Line 45:
	When adding or editing an SSO token there are two main groups of settings:		When adding or editing an SSO token there are two main groups of settings:

	# The type (not editable~~) and~~ target application ''Host Name / IP'' and ''Port''.		# The ''Auth Name'', which defines the authentication type and is not editable. And the target application ''Host Name / IP'' and ''Port''.
	# The authentication credentials. Typically this is ''username'' and 'password'', but depending on the authentication type there may be different or additional fields. For example, in the screenshot below for NTLM authentication there is an optional ''Domain'' field.		# The authentication credentials. Typically this is ''username'' and 'password'', but depending on the authentication type there may be different or additional fields. For example, in the screenshot below for NTLM authentication there is an optional ''Domain'' field.

	[[File:enportal-5.5-sso-ntlm.png\|frame\|center\|NTLM SSO token settings, notice additional Domain field.]]		[[File:enportal-5.5-sso-ntlm.png\|frame\|center\|NTLM SSO token settings, notice additional Domain field.]]

imported>Jason.nicholls: /* SSO Settings */

2014-10-24T08:57:35Z

SSO Settings

← Older revision		Revision as of 08:57, 24 October 2014
Line 46:		Line 46:

	# The type (not editable) and target application ''Host Name / IP'' and ''Port''.		# The type (not editable) and target application ''Host Name / IP'' and ''Port''.
	* The authentication credentials. Typically this is ''username'' and 'password'', but depending on the authentication type there may be different or additional fields. For example, in the screenshot below for NTLM authentication there is an optional ''Domain'' field.		# The authentication credentials. Typically this is ''username'' and 'password'', but depending on the authentication type there may be different or additional fields. For example, in the screenshot below for NTLM authentication there is an optional ''Domain'' field.

	[[File:enportal-5.5-sso-ntlm.png\|frame\|center\|NTLM SSO token settings, notice additional Domain field.]]		[[File:enportal-5.5-sso-ntlm.png\|frame\|center\|NTLM SSO token settings, notice additional Domain field.]]

imported>Jason.nicholls: /* SSO Settings */

2014-10-24T08:57:24Z

SSO Settings

← Older revision		Revision as of 08:57, 24 October 2014
Line 42:		Line 42:

	=== SSO Settings ===		=== SSO Settings ===

			When adding or editing an SSO token there are two main groups of settings:

			# The type (not editable) and target application ''Host Name / IP'' and ''Port''.
			* The authentication credentials. Typically this is ''username'' and 'password'', but depending on the authentication type there may be different or additional fields. For example, in the screenshot below for NTLM authentication there is an optional ''Domain'' field.

	[[File:enportal-5.5-sso-ntlm.png\|frame\|center\|NTLM SSO token settings, notice additional Domain field.]]		[[File:enportal-5.5-sso-ntlm.png\|frame\|center\|NTLM SSO token settings, notice additional Domain field.]]

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

2014-10-24T08:53:53Z

Managing SSO

← Older revision		Revision as of 08:53, 24 October 2014
Line 40:		Line 40:

	[[File:enportal-5.5-sso.png\|frame\|center\|Managing User and Domain-level SSO tokens.]]		[[File:enportal-5.5-sso.png\|frame\|center\|Managing User and Domain-level SSO tokens.]]

			=== SSO Settings ===

			[[File:enportal-5.5-sso-ntlm.png\|frame\|center\|NTLM SSO token settings, notice additional Domain field.]]

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

2014-10-24T08:17:40Z

Managing SSO

← Older revision		Revision as of 08:17, 24 October 2014
Line 32:		Line 32:

	== Managing SSO ==		== Managing SSO ==

			Managing SSO tokens is done via the administration interface and either the ''Provisioning'' -> ''Domains & Users'' for user and domain-level tokens, or via ''Provisioning'' -> ''Roles & Content Assignment'' for role-level tokens.

			In all three cases right-clicking on the user, domain, or role will allow the creation of new SSO tokens as shown in the screenshot below by selecting the ''New SSO'' option. Existing tokens will be visible in the ''Explorer'' tree and can be edited or deleted.

			When creating new SSO tokens the first step is to pick the authentication type, as also shown in the screenshot below. The actual list of options will depend on the PIMs installed.

	[[File:enportal-5.5-sso.png\|frame\|center\|Managing User and Domain-level SSO tokens.]]		[[File:enportal-5.5-sso.png\|frame\|center\|Managing User and Domain-level SSO tokens.]]