Login Page MaTaP UWP App

A successful login is required to be able to access the MaTaP client.

The requirements for login are as follows;

• Profile
  • 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 (an existing login name and password) are necessary.
  • These credentials carry important information regarding the user rights and capabilities of the logged in user.

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.

Manualy login is one of two ways users can access the MaTaP client. The second way is to use an NFC token 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.
Interaction with the home page is temporarily blocked as Turnaround and Commissioning Wallpaper data are downloaded.

Login Page Components

Note that the location of each component is described in the image caption.

Top: Currently selected Profile or Service, and the Status Text.
Beneath the logo: Credentials input area.
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.
• 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.
• Credentials Input Area; A username and password, for a valid user that exists on the currently selected service, are required.
• Remember Me can be used to save the credentials for the currently selected service, speeding up future logins.
• The Start Button can be used to manually navigate to the start page. However, this action is also performed automatically upon a successful login.
• 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.
• The Login Button is button is used to confirm the inputted credentials and access the service.
• The Settings Button can be used to access the Settings page, however, this should also only be used by an Admin.

NFC Login

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.

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.

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.

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.

Known Issues

When using external NFC readers such as a USB-connected device, MaTaP will not recognize any device that has been attached after the client was launched. To fix this, plug in the NFC token reader first, and launch the MaTaP client after.