scim-docs/content/overview/identity-management.md

42 lines
1.6 KiB
Markdown
Raw Normal View History

2024-08-29 10:10:19 +00:00
---
title: Identity Management
2024-08-29 21:46:48 +00:00
description : "What we speak about and in **which environment**. We must agree on some **different problematics** that exists to better understand why we use SCIM."
2024-08-29 10:10:19 +00:00
color : yellow
weight : 1
---
2024-08-29 21:46:48 +00:00
![basics of identity management](media/illus-basics.svg)
2024-08-29 10:10:19 +00:00
{{< grid >}}
2024-08-29 21:46:48 +00:00
{{< card icon="user" >}}
2024-08-29 10:10:19 +00:00
#### Authentication
Who is this user ?
{{< /card >}}
2024-08-29 21:46:48 +00:00
{{< card icon="lock" >}}
2024-08-29 10:10:19 +00:00
#### Authorization
Is this user allowed to access this resource ?
{{< /card >}}
2024-08-29 21:46:48 +00:00
{{< card icon="cloud" >}}
2024-08-29 10:10:19 +00:00
#### Storage
Where are users identity & credentials stored?
{{< /card >}}
2024-08-29 21:46:48 +00:00
{{< card icon="prov" >}}
2024-08-29 10:10:19 +00:00
#### Provisioning
How to manage & transfer users identity ?
{{< /card >}}
{{< /grid >}}
2024-08-29 21:46:48 +00:00
<img alt="illustration of losing data" src="media/illus-loose-data.svg" class="float-right">
2024-08-29 10:10:19 +00:00
### Our environment
Our digital work environment is composed of **many applications** and web services. We want a **seamless user experience** for our free software based collaboration platform. With a **Single Sign-on (SSO)** system users get a unified login and logout experience but there is a catch.
### Our problem
Traditional SSO protocols like OpenID Connect do **not support syncing user profiles across applications.** That's means :
* **users are not created by default in all apps** (only after they have logged in at least once)
* **no mechanisms to propagate the deletion of users**
* So its **not GDPR compliant** (by default)
#### In essence
2024-08-29 21:46:48 +00:00
<mark>Current existing protocols are **difficult to implement or/and to use** or are **custom for specific use case** then **non-standardized**.</mark>