Portal UI
The Portal UI (User Interface) is the public facing UI component which is the landing page for external users. It is secured; only identity provider users can login.
Once your customers or vendors are logged in, they will see the following on the Portal UI:
1. Tasks assigned to the logged-in external user.
2. Processes on which the external user has been granted access permission by the Evolve admin.
The Portal UI includes the following:
- An Angular-based SPA (Single Page Application) which supports OAuth-based authentication.
- A batch/installer to deploy to your Azure CDN (Azure Content Delivery Network).
- Registration with an identity provider.
Recommendation: To host an Angular-based Portal UI, we recommend Azure CDN, with files stored on Azure Storage . For further Azure CDN information, please see the Azure CDN site.
Resources - Azure Components
Azure Components Links |
Role in the Evolve Portal Framework |
Role Description |
---|---|---|
Portal service | Communicates with the Azure relay service to generate credentials. | |
Manages user account sign-up, sign-in, profile edit, and password resets - all from outside of the applications which have been developed to meet specific functionality. | ||
File storage | Provides file storage for hosting an Angular-based user interface (UI). | |
Offers a secured, public facing UI component which is the landing page for your external users (your vendor and customer users). | ||
Relay service |
Communicates between the relay service in the cloud and the relay worker installed in the internal network. As used in the App Service, each hybrid connection correlates to a single TCP host and port combination. |
|
Winshuttle custom built component | Relay worker | Manages the request sent to the relay service, and acts as a proxy for the internally-hosted Evolve instance. A Winshuttle custom built component. |