MACROMEDIA BREEZE-CLUSTERING BREEZE LIVE Manual de usuario Pagina 40

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 62
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 39
37
Chapter 5: Configuring advanced features
Adobe Connect Enterprise Server 6 supports technology that lets you integrate Connect Enterprise with your
existing infrastructure and adhere to your organizations security policies.
Single sign-on
Choosing a single sign-on mechanism
Single sign-on (SSO) is a mechanism that authenticates users for all applications to which they have access
permission on a network. Single sign-on uses a proxy server to authenticate users so they don’t need to log in to
Adobe Connect Enterprise. If you’ve integrated Connect Enterprise with an LDAP directory, single sign-on is useful
for managing passwords and authenticating imported users.
You must choose one of the following two single sign-on mechanisms:
HTTP header authentication Configure an authentication proxy to intercept the HTTP request, parse the user
credentials from the header, and pass the credentials to Connect Enterprise.
Microsoft NT LAN Manager (NTLM) authentication Configure NTLM to pass authentication credentials to Connect
Enterprise. Only Microsoft Internet Explorer on Microsoft Windows can negotiate NTLM authentication without
prompting the user for credentials.
Note: NTLM2 and Kerberos are not supported.
You can write your own authentication filter as well. For more information, contact Adobe Support.
Configure HTTP header authentication
When HTTP header authentication is configured, Connect Enterprise login requests are routed to an agent
positioned between the client and Connect Enterprise Server. The agent can be an authentication proxy or a software
application that authenticates the user, adds another header to the HTTP request, and sends the request to Connect
Enterprise Server. On Connect Enterprise Server, you must uncomment a Java filter and configure a parameter in
the custom.ini file that specifies the name of the additional HTTP header.
See also
Start and stop Connect Enterprise Server” on page 19
Configure HTTP header authentication on Connect Enterprise Server
To enable HTTP header authentication, configure a Java filter mapping and a header parameter on the computer
hosting Connect Enterprise Server.
1 Open the file [root_install_dir]\appserv\conf\WEB-INF\web.xml and do the following:
a Uncomment the HeaderAuthenticationFilter Java filter mapping.
<filter-mapping>
<filter-name>HeaderAuthenticationFilter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
Vista de pagina 39
1 2 ... 35 36 37 38 39 40 41 42 43 44 45 ... 61 62

Comentarios a estos manuales

Sin comentarios