External User Identity Provider
Your IT team configures and manages an identity provider to store external usernames and passwords and to provide user sign-up, password resets, password policies, and other functions out of the box.
Requirement: We only support Azure AD B2C as an identity provider. Azure AD B2C stands for Microsoft Azure Active Directory Business-to-Consumer. This component is responsible for handling user account sign-up, sign-in, profile edit, and password resets from outside of the applications developed to meet specific functionality. Azure AD B2C has its own login Portal management for which you can customize the look and feel.
In summary, Azure AD B2C is a directory and authentication service for public facing applications. It leverages identity stores outside of your company. For further information, please see the Azure AD B2C 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. |