From fa7316bee7d25afebb71c5cb5e4fd83cc884fec2 Mon Sep 17 00:00:00 2001 From: Klaus Kiefer Date: Mon, 30 Mar 2026 09:44:43 +0200 Subject: [PATCH] IdP is part of Apeiro --- .../platform-mesh/perspectives/operator-perspective.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/best-practices/platform-mesh/perspectives/operator-perspective.md b/docs/best-practices/platform-mesh/perspectives/operator-perspective.md index 6dca546..8b56d62 100644 --- a/docs/best-practices/platform-mesh/perspectives/operator-perspective.md +++ b/docs/best-practices/platform-mesh/perspectives/operator-perspective.md @@ -17,9 +17,6 @@ Instead, it provides a toolbox of core and optional elements designed to be comp Here are some examples that **fall outside the scope of Apeiro**: -- *Identity Provider (IdP)*: - Apeiro requires one or more OpenID Connect-compatible identity providers for authentication and user management. - - *Legal contracts and customer management*: Apeiro offers solely technical account management and does not include CRM functionalities or infrastructure access management for employees or something similar. It is assumed that these systems are already in place and need to be integrated.