From 662d26581c6a6adffd2d9f693267b48736839812 Mon Sep 17 00:00:00 2001
From: Stephan Lo <Stephan.Lo@telekom.de>
Date: Wed, 4 Dec 2024 14:48:53 +0100
Subject: [PATCH] feat(architecture): WiP ... just a notice on the outcome of
 today's arch session

---
 .../decision-iam-and-edf-self-containment.md  | 31 +++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 content/en/docs/solution/design/decision-iam-and-edf-self-containment.md

diff --git a/content/en/docs/solution/design/decision-iam-and-edf-self-containment.md b/content/en/docs/solution/design/decision-iam-and-edf-self-containment.md
new file mode 100644
index 0000000..2ec75aa
--- /dev/null
+++ b/content/en/docs/solution/design/decision-iam-and-edf-self-containment.md
@@ -0,0 +1,31 @@
+---
+title: eDF is self-contained and has an own IAM (WiP)
+weight: 2
+description: tbd
+---
+
+* Type: Proposal
+* Owner: Stephan Lo (stephan.lo@telekom.de)
+* Reviewers: EDF Architects
+* Status: Speculative, revision 0.1
+
+## Background
+
+tbd
+
+## Proposal
+
+==== 1 =====
+
+There is a core eDF which is self-contained and does not have any impelmented dependency to external platforms.
+eDF depends on abstractions.
+Each embdding into customer infrastructure works with adapters which implement the abstraction.
+
+==== 2 =====
+
+eDF has an own IAM. This may either hold the principals and permissions itself when there is no other IAM or proxy and map them when integrated into external enterprise IAMs.
+
+
+## Reference 
+
+Arch call from 4.12.24, Florian, Stefan, Stephan-Pierre  
\ No newline at end of file