{"ref":"content:teched-2026-xp112","page":"/content/teched-2026-xp112","json":"/content/teched-2026-xp112.json","generated":"2026-10-26","drafted_with_ai":true,"entity":{"id":"teched-2026-xp112","title":"How SAP secures enterprise AI agents with identity propagation","url":"https://www.sap.com/events/teched/berlin/flow/sap/te26/catalog/page/catalog/session/1787664725605001QBue","content_type":"talk","published_on":"source:sap-teched","explains":["artifact:btp-cloud-identity-services",{"ref":"capability:authentication","applies_to":{"ecosystems":["btp","cap"]}},{"ref":"capability:authorization","applies_to":{"ecosystems":["btp","cap"]}}],"summary":"[Cloud Identity Services](artifact:btp-cloud-identity-services) as the identity layer for AI agents as well as people: the abstract states that both are managed in one directory, that user context is propagated by token exchange, and that authorisation is enforced at every hop, so no agent holds back-end credentials. Agents from Microsoft, Google and partners take the same flow through the agent gateway. Token exchange across a hop is the [authentication](capability:authentication) side and the per-hop check the [authorisation](capability:authorization) side; what the agent gateway is, and whether it is a product, the abstract does not say. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by [Gunnar Kosche](actor:sapgunnar) and Sebastian Ries, written here from SAP's abstract; the recording is not yet published.","short":"Talk on identity propagation for AI agents in Cloud Identity Services","offers":["concepts"],"sources":[{"url":"https://developers.sap.com/build/teched","title":"SAP TechEd 2026 session catalogue feed","checked":"2026-10-11"}],"drafted_with_ai":true,"authors":["actor:sapgunnar"],"provenance":{"discovered_via":[{"source":"source:sap-teched","channel":"build/teched"}],"first_seen":"2026-10-11"},"history":[{"date":"2026-10-17","field":"explains","from":null,"to":"applies_to on capability:authentication, capability:authorization","reason":"Door scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md)."}]},"readings":{"liveness":[{"label":"Checked against the source","tier":"unknown","evidence":"nobody has checked it"},{"label":"Source reachable","tier":"unknown","evidence":"not crawled"},{"label":"Age","tier":"unknown","evidence":"no publication date"}],"compatibility":[{"label":"Version","tier":"unknown","evidence":"no version declared"},{"label":"Moved since?","tier":"unknown","evidence":"no publication date to compare"},{"label":"Findings","tier":"good","evidence":"none flagged"}],"reach":[{"value":null,"unit":"views"},{"value":null,"unit":"comments"},{"value":null,"unit":"likes"}]},"signals":null,"series":null,"edges":{"authors":[{"ref":"actor:sapgunnar","name":"Gunnar Kosche","json":"/actors/sapgunnar.json"}]}}