User Interfaces for Presentation Purposes

The following page gives guidance to GovStack members on using Sandbox UIs to demonstrate certain Building Block, Architecture or Service Design related features. Always refer to the Sandbox GitBook page: https://govstack.gitbook.io/sandbox/

To get credentials for all restricted assets, you need to contact @Nico Lueck via slack: https://govstack.slack.com/team/U032D39KF0W

GovStack Service Design and Architecture Features

User Interface

What does it demonstrate?

Public/Restricted

Further Information

User Interface

What does it demonstrate?

Public/Restricted

Further Information

Simulation

  • Civil Servant and Citizen perspective on USCT use case

  • Building Block Approach for non-techies

Public

Desktop recommended

Building Permit Frontend

  • Citizen (user) perspective on end-to-end use case (+ lightweight eGov Portal)

  • Best practice service design according to GovStack Playbook

  • Mobile First Approach

  • Use of UX/UI Service Pattern

  • Rapid Prototyping with RPC Backend

Public

https://govstack.gitbook.io/sandbox/access-demos/construction-permit-use-case

Documented service design procedure:

https://govstack.gitbook.io/sandbox/follow-methodology/best-practice-example-design-of-the-sandbox-building-permit-use-case

USCT Frontend

Civil servant (user) perspective on:

  • Identity BB Integration (UI Switch for Authentication)

  • Consent BB Integration

  • Payment BB Integration

  • A few steps of the USCT user journey

Be aware, the use case frontend does by far not demonstrate all the functionalities of a Building Block!

Public

https://govstack.gitbook.io/sandbox/access-demos/usct-use-case

USCT https://usct.playground.sandbox-playground.com/swagger-ui/index.html

API calls from use case backend to various Building Block Software/Emulators

Public

“Try out” only works when authenticated with the respective role in USCT Frontend

See diagram of all APIs here: https://github.com/GovStackWorkingGroup/sandbox-usecase-usct-backend/blob/main/docs/main.md

X-Road Central Admin Interface

X-Road Security Server Admin Interface

Overview on security server and API services registered

Restricted

X-Road admin panel:
User: xrd
PW: secret

OpenIMIS tbd

 

Restricted

 

Consent BB Admin Dashboard

Manage Data Agreements

Onboard Users

View Consent Records of Users

Developer APIs access

Manage Webhooks

Restricted

username: admin@govstack.global
password: demog2023

Note: Before you run this, you need to initiate the Consent BB server.

For developer documentation on the Consent BB admin dashboard, please refer here.

Consent BB Privacy Dashboard (link tbd)

View Data Agreements

Record Consents / Sign Data Agreement

View Consent Records and History

Restricted

Note: Before you run this, you need to initiate the Consent BB server.

For developer documentation on the Consent BB user privacy dashboard , please refer here.

GovStack CircleCI

Building Block Pipeline

Restricted

 

Building Block Software: Stand-alone Features

User Interface

What does it demonstrate?

Public/Restricted

Further Information

User Interface

What does it demonstrate?

Public/Restricted

Further Information

Issue and Use of Digital Identity

Due to limitations of the pre-authentication solution and CORS used in the interfaces, one needs to access https://api-internal.id-bb.playground.sandbox-playground.com before accessing the restricted MOSIP user interfaces.

MOSIP https://admin.id-bb.playground.sandbox-playground.com/

Role: ID Authority

Manage service centers and other organisational parameters

Restricted

More information: https://docs.mosip.io/1.2.0/modules/administration/admin-portal-user-guide

MOSIP https://pmp.id-bb.playground.sandbox-playground.com/

Role: ID Authority

Manage partner policies (e.g. which ID data a partner is authorized to request)

Restricted

More information: https://docs.mosip.io/1.2.0/modules/partner-management-services/partner-management-portal

MOSIP https://prereg.id-bb.playground.sandbox-playground.com/pre-registration-ui/#/eng

Role: Citizen

Pre-registration before citizen approaches a service center to create the ID

Restricted

Resident Email Id : Any Email ID
OTP : 111111

More information: https://docs.mosip.io/1.2.0/modules/pre-registration/pre-registration-user-guide


Per Updated Deployment Guide , pre-reg module is not deployed

MOSIP Registration
https://regclient.id-bb.playground.sandbox-playground.com/

Role: Civil Servant

Take pre-registration data and complete necessary data on site (e.g. biometric data)

Restricted

Desktop application, access rights need to be granted.

Biometric data is automatically mocked.

 

MOSIP https://resident.id-bb.playground.sandbox-playground.com/

Role: Citizen

Issue a Virtual ID (VID) or personalised cards

Public (currently Restricted)

TO Login with e-Signet click on UIN Services -> LOG IN HERE -> More Ways to Login -> Login with OTP -> Enter the UIN provided below.
UIN : 7495681570
OTP : 111111

VID PDF Password: JASO1995 (first 4 letters of name + birth year)

More information: Resident Portal User Guide | MOSIP Docs 1.2.0

MOSIP SMTP Mock

https://smtp.id-bb.playground.sandbox-playground.com/

Role: Citizen

Test e-mail OTP

Public (currently Restricted)

 

MOSIP Health Services

Role: Citizen

Test authentication with eSignet at a different government service

Public

Only authentication and consent is being demonstrated. The platform has no further functionalities!

More information: https://docs.esignet.io/esignet-end-user-guide

Giving and Managing Consent (“Data4Diabetes”)

iGrant Admin Dashboard

 

Restricted

If the dashboard login page does not load, refresh the browser page.

iGrant Registration User Web Client (link tbd)

 

 

 

Payment BB Admin UI

Video Walk through (Soon)

Payment Hub Operations Admin

Dec 2023 in rel 1.12.0

View Batch transactions

Main Batch’s and status

Sub Batches and status

View of all transactions and status

View of ID Account Mapper and Entries

Voucher Management view.

Restricted

Recommended to be restricted.

If you see an error accessing the link. Try deleting the “home” at the end of the URL.

Assumptions

  1. The infrastructure and configuration of the sandbox was designed to enable a fair amount of scalability and security. However, it does not follow all requirements in the Security Building Block. The Infrastructure BB was not developed during the time of Sandbox development.