These user experience components are used to guide the user into a workspace. There are two types of components in this folder:
- Common components used by all WASM clients irrespective of how the user will be authenticated.
- Authentication specific components that are used to create and sign in users.
Common Components
These components appear in all authentication project Index pages.
Add description of how to use the URLParams and pass through to these components… Might need to discuss separately in the WASM Authentication Projects document…
ActiveWorkspaces
This component is displayed as a user profile signs in when they have access to multiple active workspaces. The user can select a workspace from the displayed list, and they will then enter the selected workspace with as the specified user. NOTE, a user profile may have multiple active users within the same workspace with different roles or access.
If the user has only one active workspace, then the user is automatically entered into that workspace.
JoinWorkspace
This component is displayed when a user profile is accessing the website with a URL parameter that corresponds to a valid InviteUser record for a Workspace.
The InviteUser instance defines exactly how new users can be added to the workspace including: visible Applications, allowed Groups/Roles/Teams, whether they are joining a Portal, Terms of Use, Privacy Policy, etc.
After the user profile has been authenticated, the JoinWorkspace component is displayed in one of three possible modes:
- New user – in this case the user profile is added into the Workspace and assigned a set of available applications that will control their access to instance data within the Workspace.
- New portal – in this case the user profile is being added to the Workspace as an administrator of a new Portal. The user is restricted to just seeing instances created within the Portal they create so they can only ever see a subset of the instances in the Workspace as a whole. Portal administrators are allowed to invite new users and can promote/demote normal portal users to portal administrators.
- Existing Portal – in this case the user profile is added to an existing Portal within a Workspace. The user is restricted to just seeing instances created within the Portal they joined. New users to an existing portal are not by default administrators of that portal so they can not invite new users.
Authentication – Stand Alone
These components are only used by stand alone authentication projects to maintain user profiles with Username and Passwords.
ChangePassword
This component is used to change the user profile password.
ChangeSecurityQuestion
This component is used to change the security question and answer for the user profile.
SignIn
This component is used to sign in an existing user profile using an email address and password.
It also allows the user to Reset Password or Sign Up a new account.
SignUp
This component is used to create a new user profile for a user. The user will need to provide a valid email address, password, first/last name.
If the “ResetPasswordMode” in the appsettings.json configuration file is set to “SecurityQuestion”, then the component will also require the user to provide a security question and answer that will be used during password rest.