Blue Coat OPT-1000-2499-3YR User Manual Page 57

  • Download
  • Add to my manuals
  • Print
  • Page
    / 121
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 56
57
5.4.7. Using client certificates
As we have mentioned above, OPTENET can obtain authentication credentials from client
certificate data. To do so, this option has to be enabled.
On doing so, OPTENET’s own authentication server becomes a secure server, which has
to be accessed using an https protocol, rather than an http protocol. From this moment
on, data transmission between OPTENET and the user is secure, using the SSL protocol.
Taking advantage of the possibility offered by SSL communications to send client
certificates, OPTENET requests a digital certificate from users containing their
credentials. Once received, OPTENET can validate the identity of this user using the
information contained in the certificate, without the user having to enter their username
and password.
5.4.8. LDAP field to verify the client certificate
To check that the digital certificate provided by a user coincides with the contents defined
as data origin in the LDAP database, OPTENET has to consult the LDAP database.
To do so, OPTENET obtains the client certificate’s digital fingerprint and compares it to
the data in the LDAP field defined in this section. If the query is rejected, whether
because the configured field does not exist or because there is no user associated to this
digital certificate information, OPTENET offers the user the chance to authenticate
themselves by entering a username and password.
5.4.9. Activation of user alias consultation (LDAP)
When working with ICAP or ISA Server, by activating this option OPTENET can work with
an LDAP user identifier other than "Distinguished name".
Whatever the user identifier that has been configured on LDAP, in the request OPTENET
receives the "Distinguished name" from the Appliance or ISA as the user identifier. In
order solve the problem, OPTENET must carry out a consultation in order to obtain the
user identifier configured on LDAP which corresponds to the "Distinguished name"
received.
By default this option is deactivated. Once the option has been activated, the user-alias
cache must be configured (following section of the manual) and the filtering criterion field
must be established for each LDAP server that has been defined in the OPTENET
administration.
5.4.10. Life period of the user-alias association
In order to avoid saturating LDAP servers by making a consultation for every ICAP
request, OPTENET maintains an internal cache that associates a "Distinguished name"
with the user identifier configured on LDAP. In this respect, the LDAP consultation is only
made the first time. On subsequent occasions OPTENET uses the value stored in the
cache. This cache has a maximum life period, after which the entries expire, which is
when the LDAP consultation must be made again.
In this box the maximum life period must be entered in seconds.
Page view 56
1 2 ... 52 53 54 55 56 57 58 59 60 61 62 ... 120 121

Comments to this Manuals

No comments