AGENT ASSISTANT / AUTH-STORAGE
Integration Demo
Checking your shared sign-in…
One sign-in across your zone
The browser sends the shared HttpOnly cookie. Session credentials are never displayed or stored by this demo in browser storage.
Selected zone role
Roles are defined at the zone; user and group grants belong to each app. At sign-in you select one granted role for the zone. Only apps granting that role are shown. Built-in platform Admin is not an app role.
Try this with and without the Administrator role to see the server enforce access.
Effective app permissions
Permission IDs are separate from role IDs. The backend enforces them; refreshing does not select a different role. Sign in again to change your zone role.
Zone role definitions
The backend reads the catalog using managed identity. Definitions do not grant access.
Fixed session, fresh permissions
The session ends after at most 12 hours or at midnight in America/Edmonton, whichever comes first. There is no inactivity timeout. A shorter configured app lifetime still applies.
Identity responses can be reused for up to five minutes. Refresh identity requests a new permission check once the 30-second refresh window allows it.
Agent Assistant refreshes active identity caches in the background after 150 seconds. This Function demo uses auth-storage's shared cache and explicit refresh; the timer above does not send polling requests or extend your session.
Apps available to you
JSON storage
Save an expiring Redis document or durable Blob-backed JSON. Choose personal storage or share it with this app’s users.
Personal documents use your session and a user partition enforced by auth-storage. Shared documents use the app’s managed identity after verifying your sign-in.
For an expiry test, use cache storage with a 30-second TTL, save, wait, then load. Choose Blob-backed JSON for durable storage without a TTL. Nonexpiring Redis documents are separate from Blob storage. Lists and reads use the selected storage type; old test data is not migrated.
Attachments
Upload an image or another file, retrieve it privately, then try sharing it with a public link.
Backend configuration
Sign in to load the configured greeting.
Configuration indicates readiness to try a feature. Storage workload grants and network access are verified when you use it.
Auth-storage app settings
Bootstrap settings locate auth-storage and identify the environment, zone, app and managed identity. Other nonsecret application settings live on the app’s Settings tab.
An Administrator can read the allowlisted DEMO_GREETING example. Other settings are not exposed.
Use a secret without revealing it
The optional example reads one configured secret in the backend and returns only whether it is available. Workload access tokens and secret values never enter the page.
Configure the managed identity, app scope and full DEMO_SECRET_NAME on the backend, and assign Administrator to try this example.
A sibling app, discovered as a tab
- Register this backend under the intended environment, zone and app.
- Define roles at the zone, then grant a zone role to an Entra user or group on this app’s Permissions tab.
- Let the ingress worker provision the app’s public host and allow Agent Assistant to frame it.
- Reload Agent Assistant after the permission-refresh window. Its tab list comes from
zone_apps.
What this tab shares
Zone sign-in, the selected role, app-specific grants and permissions, and auth-storage services. This demo adds server-enforced private data and attachment ownership.
Caller and call context
Read the signed-in analyst’s canonical call context through this demo’s backend. Agent Assistant independently validates access to its app. No call IDs or credentials are taken from the browser. This demo does not answer calls, change availability, assign support requests, or submit tickets.
Select Read selected call for live data, or Show sample context for a fictional example.
No context loaded.
Interface map
- Identity
- GET /api/auth/me — shared zone session, selected role, effective permissions and authorized apps.
- Role catalog / settings / secrets
- GET /api/v1/apps/{env}/{zone}/{app}/{roles|settings|secrets} — backend managed identity only. Secret values stay server-side.
- Call context
- GET /api/v1/ticket-workspace/call-context — Agent Assistant validates the analyst session and returns the canonical selected call and confirmed caller.
- Storage
- /api/v2 documents, transactions and attachments — user partitions or explicitly granted workload partitions.
Try the complete flow
Refresh your identity, test a role, save and reload private JSON, compare a shared value with another authorized account, then upload a sample file and create an expiring public link. Revoke the link when finished.
Last API result
Useful for understanding response shapes. Credentials are not included.
Select a feature to begin.