awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-10-03 08:26:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update docs/documentation/platform/scim/pingone.mdx

Browse Source 
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
This commit is contained in:
Daniel Hougaard
2025-10-09 05:25:31 +04:00
committed by GitHub
co-authored by greptile-apps[bot]
parent 4333773c0d
commit b42e1108e2
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/documentation/platform/scim/pingone.mdx
+1 -1
View File
@@ -142,7 +142,7 @@ Prerequisites:
<AccordionGroup> <AccordionGroup>
<Accordion title="Why do SCIM-provisioned users have to finish setting up their account?"> <Accordion title="Why do SCIM-provisioned users have to finish setting up their account?">
Infisical's SCIM implmentation accounts for retaining the end-to-end encrypted architecture of Infisical because we decouple the **authentication** and **decryption** steps in the platform. Infisical's SCIM implementation accounts for retaining the end-to-end encrypted architecture of Infisical because we decouple the **authentication** and **decryption** steps in the platform.
For this reason, SCIM-provisioned users are initialized but must finish setting up their account when logging in the first time by creating a master encryption/decryption key. With this implementation, IdPs and SCIM providers cannot and will not have access to the decryption key needed to decrypt your secrets. For this reason, SCIM-provisioned users are initialized but must finish setting up their account when logging in the first time by creating a master encryption/decryption key. With this implementation, IdPs and SCIM providers cannot and will not have access to the decryption key needed to decrypt your secrets.
</Accordion> </Accordion>