{ "sub": "alice",
"scope": "travel:book travel:pay travel:cancel travel:refund" }{ "sub": "alice",
"authorization_details": [{
"type": "flight_booking",
"actions": ["book", "pay"],
"destination": "BER",
"maxAmount": "500 USD" }] }{ "permissions": [ "GET /fares", "GET /fares/{id}/rules", "GET /seatmap/{flight}", "POST /bookings",
"POST /payments", "calendar:read", "email:read", "cardvault:write", "web:fetch" ] }
Alice's agent cannot carry her permission to the travel platform, so today Alice lets the agent work under her credentials on the travel platform.
Alice's agent gets a signed note from her identity provider, hands it to the platform's authorization server, and receives a platform token with her delegated scope inside.
authorization_details typesThe travel platform must understand and accept the agent's authorization_details schema.
The agent asks Alice to approve a ticket purchase for any amount.
The ticket within the budget is purchased automatically. For the over-budget purchase, Alice's approval goes to a step-up authorization through Client-Initiated Backchannel Authentication (CIBA), and the platform gets a verifiable grant.
Share your experience and vote on the next briefing topic.
https://theweatherreport.ai/forms/briefing-october-21-survey/