Login Page MaTaP UWP App - Revision history

REP: /* Creating New Users */ #3991 - Updated list of required fields to second matching password.

2025-02-24T10:55:58Z

‎Creating New Users: #3991 - Updated list of required fields to second matching password.

REP: /* Creating New Users */

2025-02-18T12:22:09Z

‎Creating New Users

REP: /* Creating New Users */ replaced image

2025-02-18T12:17:09Z

‎Creating New Users: replaced image

REP: Added images

2025-02-18T12:11:11Z

Added images

REP: /* NFC Login */ added info about user creation and known issue with nfc reader

2025-02-17T15:31:55Z

‎NFC Login: added info about user creation and known issue with nfc reader

REP: Moved image

2025-01-22T07:45:01Z

Moved image

REP: /* Successful Login */

2025-01-08T14:12:48Z

‎Successful Login

REP: /* Successful Login */

2025-01-08T14:12:07Z

‎Successful Login

REP: added home page link

2025-01-08T14:09:48Z

added home page link

REP: MHM review

2025-01-08T14:02:11Z

MHM review

@@ Line 51: / Line 51: @@
 [[File:NFC_unknown.PNG|600px]]
-Once in the new user authentication form page, the RFID code is taken directly from the NFC reader, and is required to create a new user, as well as a full name, company, username and password. Telephone number and Email are optional.
+Once in the new user authentication form page, the RFID code is taken directly from the NFC reader, and is required to create a new user, as well as a full name, company, username, password, and a second matching password. Telephone number and Email are optional.
 [[File:NFC_Creation.PNG|600px]]

@@ Line 47: / Line 47: @@
 ==== Creating New Users ====
 If the RFID code on the NFC token is not associated with any user on the current database, the 'Unknown NFC' indicator and 'Request Authorization' button will be shown in the user panel. This button can be used to create a new user.
 [[File:NFC_unknown.PNG|600px]]
 Once in the new user authentication form page, the RFID code is taken directly from the NFC reader, and is required to create a new user, as well as a full name, company, username and password. Telephone number and Email are optional.
 Once created, the user panel on the root area user panel should update to match the new user's credentials, as long as their NFC token remains on the reader.
 These credentials can also be used to log in manually to the same database.

@@ Line 57: / Line 57: @@
 Once created, the user panel on the root area user panel should update to match the new user's credentials, as long as their NFC token remains on the reader.
 These credentials can also be used to log in manually to the same database.
 ==== Known Issues ====

@@ Line 7: / Line 7: @@
 ** Once a service is selected, it is unlikely a regular user will need to change it, however, this can be achieved by clicking on the Profile button at the bottom of the page.
 * '''Credentials'''
-** Valid user credentials, including an existing login name and password, are necessary.
+** Valid user credentials (an existing login name and password) are necessary.
 ** These credentials carry important information regarding the user rights and capabilities of the logged in user.
-{{Hint|''Remember Me'' must be toggled on before a successful login. Those credentials are then saved for future logins to the same service.}}
+{{Hint|''Remember Me'' must be toggled on before logging in, and the login attempt must be successful. Those credentials are then saved for future logins to the same service.}}
-Alternatively, [[Login_Page_MaTaP_UWP_App#NFC_Login|NFC tokens]] can be used to 'tap in'.
+Manualy login is one of two ways users can access the MaTaP client. The second way is to use an [[Login_Page_MaTaP_UWP_App#NFC_Login|NFC token]] to 'tap in'.
@@ Line 47: / Line 47: @@
 ==== Creating New Users ====
-If the RFID code on the NFC token is not associated with any user on the current database, the 'Unknown NFC' indicator and 'Request Authorization' button will be shown in the user panel. This button can be used to create a new user. The RFID code is taken directly from the NFC reader, and is required to create a new user, as well as a full name, company, username and password. Telephone number and Email are optional.
+If the RFID code on the NFC token is not associated with any user on the current database, the 'Unknown NFC' indicator and 'Request Authorization' button will be shown in the user panel. This button can be used to create a new user.
 Once created, the user panel on the root area user panel should update to match the new user's credentials, as long as their NFC token remains on the reader.

@@ Line 46: / Line 46: @@
 To perform an NFC login, the user simply needs to present their NFC token to an attached RFID token reader. If the user has access to the project on the terminal, the current user displayed on the [[Home_Page]] will switch to that matching the NFC token, and any additional user rights will be enabled on the client.
 <br>
 [[Category:MaTaP|Login Page MaTaP UWP App]]
 [[Category:MaTaP UWP|Login Page MaTaP UWP App]]

@@ Line 22: / Line 22: @@
-[[File:MTP_Login.PNG|thumb|800px|
+=== Login Page Components ===
 Top: Currently selected Profile or ''Service'', and the Status Text.<br>
 Beneath the logo: Credentials input area.<br>
 Bottom: Start, Profile, Login, and Settings buttons.]]
 * '''Current Profile''' gives an indication of the currently selected Profile, which carries the necessary information for connecting to a specific MaTaP project or ''Service''.

@@ Line 19: / Line 19: @@
 ==== Successful Login ====
 Once a login is successful, the client should automatically navigate to the [[Home_Page]], where the logged in user is displayed on the right side of the project header.<br>
-Interaction with the home page is temporarily blocked as Turnaround and Commissioning Wallpaper data is downloaded.
+Interaction with the home page is temporarily blocked as [[Turnaround_Wallpaper|Turnaround]] and [[Commissioning_Wallpaper]] data are downloaded.

← Older revision		Revision as of 14:09, 8 January 2025
Line 1:		Line 1:
		+	__FORCETOC__
	A successful login is required to be able to access the MaTaP client.		A successful login is required to be able to access the MaTaP client.

Line 13:		Line 14:


−	Alternatively, [[NFC_Login\|NFC tokens]] can be used to 'tap in'.	+	Alternatively, [[Login_Page_MaTaP_UWP_App#NFC_Login\|NFC tokens]] can be used to 'tap in'.
		+
		+
		+	==== Successful Login ====
		+	Once a login is successful, the client should automatically navigate to the [[Home_Page]], where the logged in user is displayed on the right side of the project header.

@@ Line 1: / Line 1: @@
 A successful login is required to be able to access the MaTaP client.
 The requirements for login are as follows;
 * '''Profile'''
-** '''How do users receive profiles in MaTaP?'''
+** Provided by the system administrators.
 ** Once a service is selected, it is unlikely a regular user will need to change it, however, this can be achieved by clicking on the Profile button at the bottom of the page.
 * '''Credentials'''
 ** Valid user credentials, including an existing login name and password, are necessary.
 ** These credentials carry important information regarding the user rights and capabilities of the logged in user.
-<br>
 [[File:MTP_Login.PNG|thumb|800px|
@@ Line 16: / Line 20: @@
 Beneath the logo: Credentials input area.<br>
 Bottom: Start, Profile, Login, and Settings buttons.]]
 === Login Page Components ===
 Note that the location of each component is described in the image caption.
-'''Current Profile'''
+* '''Current Profile''' gives an indication of the currently selected Profile, which carries the necessary information for connecting to a specific MaTaP project or ''Service''.
-* This gives an indication of the currently selected Profile, which carries the necessary information for connecting to a specific MaTaP project or ''Service''.
+* '''Status Text''' gives an indication of what to do next; whether they need to log in, the current step of the login process, or why the login may have failed.
-<br>
+* '''Credentials Input Area'''; A username and password, for a valid user that exists on the currently selected service, are required.
-'''Status Text'''
+* '''Remember Me''' can be used to save the credentials for the currently selected service, speeding up future logins.
-* This gives an indication of what to do next. This text informs the user whether they need to log in, the current step of the login process, or why the login may have failed.
+* The '''Start Button''' can be used to manually navigate to the start page. However, this action is also performed automatically upon a successful login.
-<br>
+* The '''Profile Button''' can be used to switch between services. Different services represent different projects, with their respective data and tasks. Profiles should be maintained by an Admin, and it is unlikely that regular users will need to use this button.
-'''Credentials Input Area'''
+* The '''Login Button''' is button is used to confirm the inputted credentials and access the service.
-* A Username and Password, for a valid user that exists on the currently selected service, are required.
+* The '''Settings Button''' can be used to access the Settings page, however, this should also only be used by an Admin.
-* ''Remember Me'' can be used to speed up subsequent logins by saving the credentials for the currently selected service.
-<br>
 '''Start Button'''
-* Upon successful login, the user is automatically navigated to the home page. However, this button can be used to manually navigate there if the automation fails or if the user finds themselves back on the login page.
-<br>
 '''Profile Button'''
-* This button can be used to switch between services. Different services represent different projects, with their respective data and tasks.
-* Profiles should be maintained by an Admin, and it is unlikely that regular users will need to use this button.
-<br>
 '''Login Button'''
-* This button is used to confirm the inputted credentials and access the service.
-<br>
 '''Settings Button'''
-* This button can be used to access the client Settings.
-* Settings should be maintained by an Admin, and it is unlikely that regular users will need to use this button.
 === NFC Login ===
-RFID tags can be used to quickly 'tap in' to the client, essentially skipping the need to enter a username and password.
+MaTaP clients are often found on-site, presenting a so called "kiosk" or "terminal" usecase. These clients are pre-logged in for any contractor to use. However, these terminals have Read-only restrictions, and in order to make any changes or read sensitive data, which would require additional user rights, the user would first need to verify their identity.
 <br>
 [[Category:MaTaP|Login Page MaTaP UWP App]]
 [[Category:MaTaP UWP|Login Page MaTaP UWP App]]