Eternet Portal Documentation
User Profile
Identity source
The profile page reads its profile card from the server-side Keycloak session. It is an identity summary and should not be confused with editing the full identity-provider account unless a specific update operation is exposed.
Availability
Profile information requires a valid authenticated session and configured Keycloak integration.
Profile as an identity summary
The Profile page shows identity information associated with the current signed-in user. Its server-rendered route reads the Keycloak session and passes that information to a profile card. This makes the page useful for confirming which account is currently active, especially when operators work across multiple environments or roles. The authoritative identity comes from the configured identity provider rather than from an independent profile database maintained by the portal.
Identity attributes can include a display name, email, username, and other fields returned in the session. Not every attribute is guaranteed to exist for every account, and a user may have different display values across providers. The profile view should therefore be treated as a session summary. It should not be presented as proof that the user can edit every attribute or that changing a displayed value will update the identity provider. Account edits such as password, MFA, email verification, or profile changes require a corresponding Keycloak or identity-service operation.
Session and account troubleshooting
If the profile appears empty or shows an unexpected user, first confirm the authentication session and the identity provider configuration. A stale browser session, expired token, missing claim mapping, or alternate username/email attribute can affect what the page displays. Logging out and signing in again may refresh the session, but support staff should avoid asking a user to share tokens or credentials. The portal should expose only the minimum identity attributes needed for its workflow and should not place access tokens in page URLs or visible client logs.
Profile identity also matters to other portal features: API requests use the authenticated session, and access-control decisions are ultimately based on the identity and claims recognized by backend services. A displayed name is not the authorization key. Administrators should use stable subject IDs where available when investigating a grant or audit record.
Customer value and scope
A clear profile summary improves trust by making account context visible and helping users confirm which identity is active before they perform operational actions. It is especially helpful in shared support environments where switching accounts can otherwise be confusing. During a demonstration, show the signed-in profile and explain that authentication is handled by Keycloak. Be clear that the current page is primarily read-only unless an explicit edit workflow is available. Identity lifecycle, password policy, and MFA configuration remain responsibilities of the identity provider and its administrators.
Privacy and support boundaries
Profile details should be displayed only to the signed-in user unless an administrator workflow explicitly permits broader visibility. Support teams should avoid copying identity claims into public tickets and should never request a password or bearer token. When escalating a session issue, use a non-secret account identifier and the time of the failed request. These practices help preserve the trust boundary between the portal and the identity provider.