Skip to content

Commit

Permalink
Update docs/ocis/identity-provider/_index.md
Browse files Browse the repository at this point in the history
Co-authored-by: Martin <[email protected]>
  • Loading branch information
EParzefall and mmattel authored Nov 14, 2023
1 parent 049815b commit dd461e6
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/ocis/identity-provider/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,4 +10,4 @@ geekdocCollapseSection: true

## Overview

oCIS provides an internal identity provider which can be configured via the [IDP service](../../services/idp/), or connect to an external identity provider like Keycloak (in connection with openLDAP) or Microsoft Active Directory Federation Service (ADFS) (in connection with MS Active Directory). Entrada ID (formerly Azure AD) is in preperation, but not yet documented and might need some small fixes and for certain functions a LDAP/AD connection.
oCIS provides out of the box a minimal OpenID Connect provider via the [IDP service](../../services/idp/) and a minimal LDAP service via the [IDM service](../../services/idm/). Both services are limited in the provided functionality, see the [admin documentation](https://doc.owncloud.com/ocis/next/deployment/services/s-list/idp.html) for details, and can be used for small environments like up to a few hundred users. For enterprise environments, it is highly recommended using enterprise grade external software like KeyCloak plus openLDAP or MS ADFS with Active Directory, which can be configured in the respective service. Entrada ID (formerly Azure AD) is in preparation, but not yet released or documented and might need some small fixes, and for certain functions a LDAP/AD connection.

0 comments on commit dd461e6

Please sign in to comment.