mirror of
https://github.com/awatertrevi/infisical.git
synced 2026-10-07 16:27:40 +00:00
misc: removed outdated faq section
This commit is contained in:
@@ -24,18 +24,3 @@ SCIM providers:
|
|||||||
- [Okta SCIM](/documentation/platform/scim/okta)
|
- [Okta SCIM](/documentation/platform/scim/okta)
|
||||||
- [Azure SCIM](/documentation/platform/scim/azure)
|
- [Azure SCIM](/documentation/platform/scim/azure)
|
||||||
- [JumpCloud SCIM](/documentation/platform/scim/jumpcloud)
|
- [JumpCloud SCIM](/documentation/platform/scim/jumpcloud)
|
||||||
|
|
||||||
**FAQ**
|
|
||||||
|
|
||||||
<AccordionGroup>
|
|
||||||
<Accordion title="Why do SCIM-provisioned users have to finish setting up their account?">
|
|
||||||
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.
|
|
||||||
</Accordion>
|
|
||||||
</AccordionGroup>
|
|
||||||
|
|||||||
Reference in New Issue
Block a user