Authentication Workflows - Revision history

IVSWikiBlue at 14:42, 25 June 2026

2026-06-25T14:42:34Z

← Older revision		Revision as of 14:42, 25 June 2026
Line 3:		Line 3:
	{{Grid 2 - Grid \| left = There are three different authentication methods that can be used for VALT.		{{Grid 2 - Grid \| left = There are three different authentication methods that can be used for VALT.

	#Local		#[[#Local Authentication\|Local Authentication]]
	#LDAP~~/LDAPS~~		#[[#LDAP Authentication\|LDAP Authentication]]
	#SSO		#[[#Single Sign-On (SSO)\|Single Sign-On (SSO)]]
	\| right =		\| right =
	{{Aside \| content = Any combination of these can be implemented and used at the same time.}}		{{Aside \| content = Any combination of these can be implemented and used at the same time.}}
Line 26:		Line 26:
	{{hr}}		{{hr}}

	{{Manual lvl 2 \| title = SSO ~~Authentication~~ \| content =		{{Manual lvl 2 \| title = Single Sign-On (SSO) \| content =
	SSO accounts are automatically created when a user logs in for the first time. The user can be placed in the proper group automatically upon login by mapping SSO attributes to a user group within VALT.}}		SSO accounts are automatically created when a user logs in for the first time. The user can be placed in the proper group automatically upon login by mapping SSO attributes to a user group within VALT.}}

IVSWikiBlue at 14:38, 25 June 2026

2026-06-25T14:38:28Z

← Older revision		Revision as of 14:38, 25 June 2026
Line 1:		Line 1:
	~~__TOC__~~		{{Article - Manual \| content = <onlyinclude>
	{{Article ~~\| title = Authentication Workflows~~ \| content =		<h1>Authentication Methods</h1>
	<~~onlyinclude~~>		{{Grid 2 - Grid \| left = There are three different authentication methods that can be used for VALT.
	There are three different authentication methods that can be used for VALT:

	~~<b>~~		#Local
	*Local ~~Authentication~~		#LDAP/LDAPS
	*LDAP ~~Authentication~~		#SSO
	*SSO ~~Authentication~~		\| right =
	~~</b>~~		{{Aside \| content = Any combination of these can be implemented and used at the same time.}}
			}}

	{{hr}}		{{hr}}

	~~<h2>~~Local Authentication~~</h2>~~		{{Manual lvl 2 \| title = Local Authentication \| content =
	Local accounts are created and assigned to groups within VALT. Local accounts can be created manually or imported from a [[Importing_Users_from_a_file\|list]].		Local accounts are created and assigned to groups within VALT. Local accounts can be created manually or imported from a [[Importing_Users_from_a_file\|list]].}}

	{{img - resize \| file = auth_local.jpg}}		{{img - resize \| file = auth_local.jpg}}
Line 19:		Line 19:
	{{hr}}		{{hr}}

	~~<h2>~~LDAP Authentication~~</h2>~~		{{Manual lvl 2 \| title = LDAP Authentication \| content =
	LDAP accounts can be imported manually using an LDAP search and lookup tool within the software or imported automatically on a schedule based on group.		LDAP accounts can be imported manually using an LDAP search and lookup tool within the software or imported automatically on a schedule based on group.}}

	{{img - resize \| file = auth_ldap.jpg}}		{{img - resize \| file = auth_ldap.jpg}}
Line 26:		Line 26:
	{{hr}}		{{hr}}

	~~<h2>~~SSO Authentication~~</h2>~~		{{Manual lvl 2 \| title = SSO Authentication \| content =
	SSO accounts are automatically created when a user logs in for the first time. The user can be placed in the proper group automatically upon login by mapping SSO attributes to a user group within VALT.		SSO accounts are automatically created when a user logs in for the first time. The user can be placed in the proper group automatically upon login by mapping SSO attributes to a user group within VALT.}}

	*VALT's SSO uses <b>Just-In-Time (JIT) Provisioning</b>.
	**<em>Users are reevaluated and assigned to groups each time they log in, based on a [[Single_Sign-On_(SSO)#User_Mapping \| group membership]] attribute being passed.</em>
	*If a user does <u>NOT</u> have a user mapping associated with their account, the user gets moved to "<b>Users without Group</b>" and has restricted access.
	*If a user's user mapping changes, they will be moved to the correct group upon their next SSO sign-in.
	**<em>Correct mapping is based on the SSO mapping created in VALT and the attribute/pair value being passed from the IdP.</em>

	~~{{hr - 2~~}}

	{{img - resize \| file = SSO Flow Chart.png}}		<center>{{img - resize \| file = SSO Flow Chart.png \| width = 600px}}</center>

	~~</onlyinclude>~~		{{Top of Page}}
			</onlyinclude>}}
	{{hr}}

	~~[[VALT SSO\| ⤺ Back to VALT SSO Main Page]]~~
	}}

IVSWikiBlue at 20:13, 1 April 2024

2024-04-01T20:13:30Z

← Older revision		Revision as of 20:13, 1 April 2024
Line 30:		Line 30:

	*VALT's SSO uses <b>Just-In-Time (JIT) Provisioning</b>.		*VALT's SSO uses <b>Just-In-Time (JIT) Provisioning</b>.
	**<em>Users are reevaluated and assigned to groups each time they log in, based on a group membership attribute being passed.</em>		**<em>Users are reevaluated and assigned to groups each time they log in, based on a [[Single_Sign-On_(SSO)#User_Mapping \| group membership]] attribute being passed.</em>
	*If a user does <u>NOT</u> have a user mapping associated with their account, the user gets moved to "<b>Users without Group</b>" and has restricted access.		*If a user does <u>NOT</u> have a user mapping associated with their account, the user gets moved to "<b>Users without Group</b>" and has restricted access.
	*If a user's user mapping changes, they will be moved to the correct group upon their next SSO sign-in.		*If a user's user mapping changes, they will be moved to the correct group upon their next SSO sign-in.

IVSWikiBlue at 20:12, 1 April 2024

2024-04-01T20:12:26Z

← Older revision		Revision as of 20:12, 1 April 2024
Line 30:		Line 30:

	*VALT's SSO uses <b>Just-In-Time (JIT) Provisioning</b>.		*VALT's SSO uses <b>Just-In-Time (JIT) Provisioning</b>.
	**<em>Users are reevaluated and assigned to groups each time they log in, based on ~~the~~ group membership attribute being passed.</em>		**<em>Users are reevaluated and assigned to groups each time they log in, based on a group membership attribute being passed.</em>
	*If a user does <u>NOT</u> have a user mapping associated with their account, the user gets moved to "<b>Users without Group</b>" and has restricted access.		*If a user does <u>NOT</u> have a user mapping associated with their account, the user gets moved to "<b>Users without Group</b>" and has restricted access.
	*If a user's user mapping changes, they will be moved to the correct group upon their next SSO sign-in.		*If a user's user mapping changes, they will be moved to the correct group upon their next SSO sign-in.

IVSWikiBlue at 15:47, 1 April 2024

2024-04-01T15:47:32Z

← Older revision		Revision as of 15:47, 1 April 2024
Line 40:		Line 40:

	</onlyinclude>		</onlyinclude>

			{{hr}}

	[[VALT SSO\| ⤺ Back to VALT SSO Main Page]]		[[VALT SSO\| ⤺ Back to VALT SSO Main Page]]
	}}		}}

IVSWikiBlue at 15:46, 1 April 2024

2024-04-01T15:46:24Z

← Older revision		Revision as of 15:46, 1 April 2024
Line 40:		Line 40:

	</onlyinclude>		</onlyinclude>
			[[VALT SSO\| ⤺ Back to VALT SSO Main Page]]
	}}		}}

IVSWikiBlue at 21:18, 29 March 2024

2024-03-29T21:18:44Z

← Older revision		Revision as of 21:18, 29 March 2024
Line 15:		Line 15:
	Local accounts are created and assigned to groups within VALT. Local accounts can be created manually or imported from a [[Importing_Users_from_a_file\|list]].		Local accounts are created and assigned to groups within VALT. Local accounts can be created manually or imported from a [[Importing_Users_from_a_file\|list]].

	{{img - ~~no_click~~ \| file = auth_local.jpg}}		{{img - resize \| file = auth_local.jpg}}

	{{hr}}		{{hr}}
Line 22:		Line 22:
	LDAP accounts can be imported manually using an LDAP search and lookup tool within the software or imported automatically on a schedule based on group.		LDAP accounts can be imported manually using an LDAP search and lookup tool within the software or imported automatically on a schedule based on group.

	{{img - ~~no_click~~ \| file = auth_ldap.jpg}}		{{img - resize \| file = auth_ldap.jpg}}

	{{hr}}		{{hr}}
Line 37:		Line 37:
	{{hr - 2}}		{{hr - 2}}

	{{img - ~~no_click~~ \| file = SSO Flow Chart.png}}		{{img - resize \| file = SSO Flow Chart.png}}

	</onlyinclude>		</onlyinclude>
	}}		}}

IVSWikiBlue at 12:47, 28 March 2024

2024-03-28T12:47:07Z

← Older revision		Revision as of 12:47, 28 March 2024
Line 29:		Line 29:
	SSO accounts are automatically created when a user logs in for the first time. The user can be placed in the proper group automatically upon login by mapping SSO attributes to a user group within VALT.		SSO accounts are automatically created when a user logs in for the first time. The user can be placed in the proper group automatically upon login by mapping SSO attributes to a user group within VALT.

	*VALT uses <b>Just-In-Time (JIT) Provisioning</b>.		*VALT's SSO uses <b>Just-In-Time (JIT) Provisioning</b>.
	**<em>Users are reevaluated and assigned to groups each time they log in, based on the group membership attribute being passed.</em>		**<em>Users are reevaluated and assigned to groups each time they log in, based on the group membership attribute being passed.</em>
	*If a user does <u>NOT</u> have a user mapping associated with their account, the user gets moved to "<b>Users without Group</b>" and has restricted access.		*If a user does <u>NOT</u> have a user mapping associated with their account, the user gets moved to "<b>Users without Group</b>" and has restricted access.

IVSWikiBlue at 21:46, 27 March 2024

2024-03-27T21:46:17Z

← Older revision		Revision as of 21:46, 27 March 2024
Line 31:		Line 31:
	*VALT uses <b>Just-In-Time (JIT) Provisioning</b>.		*VALT uses <b>Just-In-Time (JIT) Provisioning</b>.
	**<em>Users are reevaluated and assigned to groups each time they log in, based on the group membership attribute being passed.</em>		**<em>Users are reevaluated and assigned to groups each time they log in, based on the group membership attribute being passed.</em>
	*If a user does <u>NOT</u> have a user mapping associated with their account, user gets moved to "<b>Users without Group</b>" and has restricted access.		*If a user does <u>NOT</u> have a user mapping associated with their account, the user gets moved to "<b>Users without Group</b>" and has restricted access.
	*If a user's user mapping changes, they will be moved to the correct group upon their next SSO sign-in.		*If a user's user mapping changes, they will be moved to the correct group upon their next SSO sign-in.
	**<em>Correct mapping is based on the SSO mapping created in VALT and the attribute/pair value being passed from the IdP.</em>		**<em>Correct mapping is based on the SSO mapping created in VALT and the attribute/pair value being passed from the IdP.</em>

IVSWikiBlue at 21:45, 27 March 2024

2024-03-27T21:45:44Z

← Older revision		Revision as of 21:45, 27 March 2024
Line 29:		Line 29:
	SSO accounts are automatically created when a user logs in for the first time. The user can be placed in the proper group automatically upon login by mapping SSO attributes to a user group within VALT.		SSO accounts are automatically created when a user logs in for the first time. The user can be placed in the proper group automatically upon login by mapping SSO attributes to a user group within VALT.

	*VALT uses Just-In-Time (JIT) Provisioning.		*VALT uses <b>Just-In-Time (JIT) Provisioning</b>.
	**Users are reevaluated and assigned to groups each time they log in, based on the group membership attribute being passed.		**<em>Users are reevaluated and assigned to groups each time they log in, based on the group membership attribute being passed.</em>
	*If a user does NOT have a user mapping associated with their account, user gets moved to "Users without Group" and has restricted access		*If a user does <u>NOT</u> have a user mapping associated with their account, user gets moved to "<b>Users without Group</b>" and has restricted access.
	*If a user's user mapping changes, they will be moved to the correct group upon their next SSO sign-in		*If a user's user mapping changes, they will be moved to the correct group upon their next SSO sign-in.
			**<em>Correct mapping is based on the SSO mapping created in VALT and the attribute/pair value being passed from the IdP.</em>

	{{hr - 2}}		{{hr - 2}}