Cisco Cisco Web Security Appliance S670 Betriebsanweisung

Seite von 784
 
14-9
Cisco IronPort AsyncOS 7.0 for Web User Guide
OL-23079-01
Chapter 14      Controlling Access to SaaS Applications
Configuring the Appliance as an Identity Provider
Note
If you intend to use multiple Web Security appliances with SaaS Access Control, 
you must enter the same Identity Provider Domain Name for each Web Security 
appliance. If you have only one appliance, you can use the appliance hostname as 
the Identity Provider Domain Name. For more information, see 
Step 4
In the Identity Provider Entity ID field, enter the text you want to use that 
uniquely identifies this Web Security appliance as an identity provider to all SaaS 
applications it will communicate with.
A URI format based string is recommended, but you can enter any unique string. 
The URI string does not have to be network accessible. Record the value you enter 
here because you will need to use the same value when you configure the SaaS 
application for single sign-on. 
Note
If you intend to use multiple Web Security appliances with SaaS Access Control, 
you must enter the same Identity Provider Entity ID for each Web Security 
appliance. For more information, see 
Step 5
Configure a signing certificate the appliance should use when it communicates 
using a secure connection (in the SAML flow) with service providers. You can use 
either of the following methods to configure the certificate: 
  •
Generated certificate and key. Go to step 
  •
Uploaded certificate and key. Go to step 
Note
If the appliance has both an uploaded certificate and key pair and a 
generated certificate and key pair, it only uses the certificate and key pair 
currently selected in the Signing Certificate section.
Step 6
To generate a certificate and key:
a.
Click the Use Generated Certificate and Key option.
b.
Click Generate New Certificate and Key.
c.
In the Generate Certificate and Key dialog box, enter the information to 
display in the signing certificate.