Step-by-Step Process & Entities

Entities Involved

1. End User (Browser)

• The person accessing the Partner Portal
• Can be a contractor employee or grid company employee
• Uses their email and password to log in

2. Blazor WebAssembly Application (Frontend)

• The Partner Portal web interface running in the user's browser
• Built with .NET Blazor WebAssembly
• Location: Source/EGU.PartnerPortal.Web
• Runs entirely client-side (in the browser)

3. MSAL.js Library

• Microsoft Authentication Library for JavaScript
• Embedded in the Blazor app
• Handles all OAuth2/OpenID Connect communication
• Manages tokens and session state

4. Microsoft Entra ID (CIAM Tenant)

• Microsoft's cloud identity service
• Stores user credentials and profiles
• Tenant ID: 6073ce8b-73f3-4df4-9b80-5e40cdc6965f
• Issues JWT tokens after successful authentication
• Hosted by Microsoft (external service)

5. ApiService (Backend API)

• The Partner Portal backend REST API
• Built with ASP.NET Core
• Location: Source/EGU.PartnerPortal.ApiService
• Validates JWT tokens on every API request
• Enforces authorization policies