How tomaafloen/eeidtestapp works
This is a small browser-based OIDC test application. A user signs in through the page, MSAL handles the redirect-based authentication with Entra External ID, and the app displays account details and ID-token claims. The user can separately request an access token; the app tries silent acquisition first and falls back to an interactive redirect. The README identifies the HTML page as the UI and documents the Entra integration. The page’s exact event-wiring details and the loading relationship between files were not sampled, so those connections are not asserted.
Main entry points: app.js Authentication logic · config.js MSAL settings · index.html Application page
Components 8
Browser interface
- Application page
index.html
Authentication
- Authentication logic
app.js - MSAL settings
config.js - MSAL.js
Results
- Account and claims display
app.js - Access token display
app.js
Other components
- User
- Entra External ID
Connections 9
- User → Application page: uses
README.md - User → Authentication logic: requests sign-in
README.md - Authentication logic → MSAL.js: calls
app.js - MSAL.js → Entra External ID: redirects for auth
- MSAL settings → Entra External ID: sets authority
config.js - Authentication logic → Account and claims display: renders
app.js - Authentication logic → Access token display: renders
app.js - User → Authentication logic: requests token
README.md - Authentication logic → MSAL.js: acquires token
app.js