Authentication

Authentication is the act of verifying users' identities based on credentials that those users present.

Authentication overview
Authentication depends on several components.
JAVA-based client authentication (JAAS)
Content Platform Engine accepts requests either through a standard Java EE EJB or through the Content Engine Web service. Clients of the Content Platform Engine Java API have the option of choosing to use either of these transport layers.
Single sign-on integrations via JAAS
The implementation of the Content Platform Engine server as a Java EE application allows it to take advantage of integrations between the Java EE application-server vendors and the leading single sign-on (SSO) solution providers such as IBM® Security Verify Directory and CA/Netegrity's SiteMinder. These are the two solutions that are currently qualified for end-to-end Content Cortex deployments.
Single sign-on integrations via Content Engine API Bearer Token Authentication
The Bearer Token Authentication support added to the Content Engine API allows any client, regardless of whether it runs in an application server, standalone java application, or servlet, to pass a user's identity for Single sign-on to the Content Platform Engine server. The SSO capability is restricted to OAuth or OIDC authentication tokens that are passed to the Content Platform Engine server on the standard HTTP Authorization header as a Bearer token on the Content Engine WSI request.
Web-Services-based client authentication via WS-Security
Two WS-Security profiles, the Username Token profile and the Kerberos profile, are supported by Content Cortex. Support for additional standard profiles, as well as non-standard WS-Security compliant approaches, can be integrated with Content Cortex Web services, using the Content Cortex Web Service Extensible Authentication Framework.
IBM Content Navigator authentication
IBM Content Navigator is a web client that provides users with a web console for working with content stored on IBM Content Cortex repositories.
Kerberos for Content Platform Engine
Kerberos support is available to clients of the Content Platform Engine Web Services API, the Content Platform Engine .NET API, and the Content Platform Engine COM API. Many third-party COM and Web-service-based applications are also available that can take advantage of this Kerberos support.
OIDC and OAuth identity providers
You can use Open ID Connect or OAuth 2.0 authentication to manage user access and enable automatic registration of users for your environment.