Historic AtlasPERSONAL SETTINGS / LOCAL PREVIEW
A SMALL SPACE THAT'S YOURS

Your corner
of the atlas.

Keep your preferences here. Keep identity with its source. Explore how the application separates the two, using a fictional profile.

01

A familiar appearance.

Light, dark, or whatever feels right for your browser. This local setting resets when the page reloads.

Appearance: system · local preference object is empty (default).
Inspect the preference API contract

PATCH /api/users/me merges valid preference keys. Unknown keys and values are rejected. The backend requires CSRF and a session; this sandbox only simulates the preference/CSRF checks.

Language is not stored as a preference until a feature needs it.

02

A face, not a tracking request.

Try a PNG or JPEG up to 2 MB and 4096 × 4096 pixels. This browser preview checks the file signature, crops the largest centered square and produces a 256 × 256 PNG.

No image selected. Initials are shown instead.

The specified application performs these checks on its backend, stores the PNG beside the user and includes it in backups. This local canvas preview is not a security boundary or persistent avatar service.

03

One person. Their own record.

GET /api/users/me returns the current user's record, never another person's. No user-list or by-ID endpoint exists. Avatar writes require CSRF; the private image response has nosniff, an ETag and private caching, or 404 when absent.

Profile claims refresh from the ID token at every login. Roles remain in the token—not in the application's User record.

Created once.

On first login, the user listener responds to an auth event. A unique realm subject plus read-after-conflict makes simultaneous creation idempotent. Auth does not depend on the user module.

Login comes first.

A failed user write is logged but does not block login. A later login retries; GET /api/users/me can create a missing record on demand. Imported profile claims are optional and limited to feature needs.

Identity outlives an account.

Deleting a Keycloak account currently leaves the User record so location audit references retain meaning. Personal-data cleanup is future feature work—not something this demo performs.

No real account, login, API, database or external image request is connected. Local uploads remain in this tab. Choose only an image you have permission to use.

AN EXPLICIT CHOICE

A copy, only when asked.

The intended backend hashes the trimmed, lower-case email with SHA-256, requests a 256px image from the fixed gravatar.com host once, then processes and stores a local PNG copy. Five-second timeout, at most 1 MB, same-host redirects only. The browser never contacts Gravatar.

No email: 409. No image: 404. Provider failure: 502. A saved copy does not follow later provider changes until requested again.

This policy preview will not contact Gravatar or send even the sample email hash.