Supported Authentication Tools
Composer supports several approaches to authenticating users. Your organization must choose the best approach given your existing constraints and objectives.
Composer provides basic login access to the Composer application. See Authorize Composer Access.
X.509 client certificate authentication can be used to provide single sign-on capabilities, although it does not support auto-provisioning of user accounts. See Configure Client Certificate Authentication.
SAML (Security Assertion Markup Language) can be used to provide single sign-on capabilities. See Configure Composer to Support SAML.
Kerberos can be used to provide single sign-on capabilities. See Configure Kerberos Single Sign-On (SSO) Settings.
Trusted Access can be used to allow for machine-to-machine authorization of Composer resources when embedded in your application. It allows users to log in once to the parent application and yet have their security information propagated to Logi Composer, creating a seamless and secure user experience. See Trusted Access.
Logi Analytics recommends using Trusted Access for all embed-related workflows.
The OAuth 2.0 protocol as well as the OAuth 2.0 Implicit Flow can be used for authentication and authorization. See Use OAuth 2.0 to Access Composer.
LDAP (Lightweight Directory Access Protocol) can be used to enable directory-based access to Composer. Composer can connect to an organization’s Active Directory (AD) and OpenLDAP directory services using configured LDAP settings. See Use Lightweight Directory Access Protocol (LDAP) With Composer.
Composersupervisors can enable or disable Composer's authentication services as required. The available services are listed on the Security Services tab:
Log into Composer as a supervisor.
Select to access the supervisor menu and then select Security.
The Security page appears. It consists of four tabs: Security Services, SAML Settings, LDAP Settings, and Kerberos Settings. The Security Services tab is selected. Note that the SAML Settings, LDAP Settings, and Kerberos Settings tabs are accessible only when the corresponding service is enabled on the Security Services tab.
Settings for x.509, Kerberos SSO, and OAuth authentication are handled using the
Enabling or disabling any of these security services requires a restart of the Composer service. Basically, any time you toggle a security feature, the Composer service needs to be restarted before the change takes effect. The following toggle status may appear for each of the authentication services: Started, Stopped, Will start or stop on next restart. See Enable or Disable a Security Service.
When working with security authentication services, bear in mind that you cannot use them all at the same time. If you toggle a particular security service on, others will become disabled. If you want to use a security service that is disabled, you must toggle the running services off and then start the service you want. The following table describes the compatibility of the security services.
|Security Service||Can Be Used With|
|LDAP||Kerberos, x509, OAuth|
|OAuth||SAML, LDAP, Kerberos, x509|