The web.xml file uses generic filters that call into the authentication subsystem.
There is no need to edit the web.xml file. There is no need to specify the same parameters to different components in multiple configuration files. Common parameters are shared and specified in a single place. 
There is no danger of compatibility issues between sub-components, as these have all been pre-selected. Subsystems for all supported authentication types are pre-wired and there is no need to edit template configuration. The main benefits of the authentication subsystem are: User registry export (the automatic population of the user and authority database). Web browser, Microsoft SharePoint protocol, and WebDAV Single Sign-On (SSO). Password-based authentication for web browsing, Microsoft SharePoint protocol, FTP, and WebDAV. An authentication subsystem is a coordinated stack of compatible components responsible for providing authentication and identity-related functionality to Content Services.Ĭontent Services offers multiple implementations of the authentication subsystem, each engineered to work with one of the different types of back-end authentication server that you have available in your enterprise.Īn authentication subsystem provides the following functions: Authentication subsystemsĪuthentication is one of the categories of the Content Services subsystem. Users and groups can also be managed from the Share Admin Tools, but it’s more common to sync with a Directory Service, which is discussed here.Īuthentication subsystems and authentication chains are discussed first as an understanding of those is necessary when configuring authentication and synchronization. 
Set up how user and group information should be synced (imported) with Content Services. Set up if users should be authenticated with the database, LDAP, SSO etc. Use this information to manage user authentication.
0 kommentar(er)
