Portal Service
The Portal service is a public facing service secured by the identity provider; only valid, authenticated users of the identity provider can communicate with the Portal service.
The Portal service is deployed on your Azure Function and communicates with the Azure relay service to generate credentials.
The Portal UI securely communicates with the Portal service to acquire the connection information necessary to relay requests. Next, the Portal UI raises a request to securely relay requests to the internal network.
Recommendation: We recommend Azure Functions as a hosting Portal service. Azure Functions is a .NET Core based serverless computing service that allows you to run event-triggered code without needing to explicitly provision or manage infrastructure. It’s a cloud service available on-demand providing all the continually updated infrastructure and resources required to run your applications. For further information, please see the Azure Functions 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. |