A SAML service provider connector (an SP connector) specifies how a BIG-IP system, configured as a SAML Identity Provider (IdP), connects with an external service provider.

You can use one or more of these methods to configure SAML service provider (SP) connectors in Access Policy Manager.

• From metadata - Obtain a metadata file from the vendor and import it into Access Policy Manager. The advantage to this method is that the vendor provides the majority of all required data, including certificates. You can complete the configuration by simply typing a unique name for the SP connector, a very few additional required fields, and browsing to and importing the file. Access Policy Manager then configures the SP connector.
• From template - Use templates that Access Policy Manager provides for some vendors; for example, Google. The advantages to this method are that:
  • Most required data is included in the template
  • Additional required data is minimal. You can obtain it and certificates from the vendor
  After you select a template and type data into a few fields, Access Policy Manager configures the SP connector.
• Custom - Obtain information from the vendor and type the settings into the Configuration utility. To use this method, you must also obtain certificates from the vendor and import them into the BIG-IP system. Use this method when a metadata file or a template for an SP connector is not available.

An IdP connector specifies how a BIG-IP system, configured as a SAML service provider (SP), connects with an external SAML identity provider (IdP).

You can use one or more of these methods to configure SAML identity provider (IdP) connectors in Access Policy Manager (APM).

• From metadata - Obtain a metadata file from the vendor and import it into APM. The advantage to this method is that the vendor provides all required data, including the certificate. You can complete the configuration by simply typing a unique name for the identity provider, and browsing to and importing the file. APM imports the certificate to the BIG-IP system and configures the SAML IdP connector.
• From template - Use templates that APM provides for some vendors. The advantages to this method are that:
  • Most required data is included in the template. (Note that the certificate is not included.)
  • Additional required data is minimal and is available from the vendor.
  APM configures the SAML IdP connector. You must obtain a certificate from the vendor and import it into the BIG-IP system.
• Custom - Research the identity provider requirements and type all settings into the Configuration utility. Use this method when a metadata file or a template for an identity provider is not available. APM configures the SAML IdP connector. You must obtain a certificate from the vendor and import it into the BIG-IP system.
• IdP Automation - Provide files with cumulative IdP metadata on remote systems, then configure BIG-IP IdP automation to poll the files periodically and create IdP connectors and bind them to a specific service provider (SP) service.

1. On the Main tab, click Local Traffic > Virtual Servers. The Virtual Server List screen opens.
2. Click the Create button. The New Virtual Server screen opens.
3. In the Name field, type a unique name for the virtual server.
4. In the Destination Address field, type the IP address for a host virtual server. This field accepts an address in CIDR format (IP address/prefix). However, when you type the complete IP address for a host, you do not need to type a prefix after the address.
5. In the Service Port field, type 443 or select HTTPS from the list.
6. For the HTTP Profile setting, verify that the default HTTP profile, http, is selected.
7. For the SSL Profile (Client) setting, from the Available list, select the name of the Client SSL profile you previously created, and using the Move button, move the name to the Selected list.
8. For the SSL Profile (Server) setting, from the Available list, select the name of the Server SSL profile you previously created, and using the Move button, move the name to the Selected list.
9. Click Finished.

1. On the Main tab, click Access Policy > SAML > BIG-IP as IdP. The BIG-IP as IdP screen displays a list of SAML IdP services.
2. Click Create. The Create New IdP Service popup screen displays.
3. In the IdP Service Name field, type a unique name for the SAML IdP service.
4. In the IdP Entity ID field, type a unique identifier for the IdP (this BIG-IP system). Include the URI that points to the virtual server with the BIG-IP system and a unique path. For example, if you type https://bigip-idp/idp, https://bigip-idp should point to the virtual server you use for the BIG-IP system as a SAML IdP and /idp is a string that distinguishes one IdP from another when this BIG-IP system supports multiple SAML IdP services. The path portion on the IdP Entity ID is not a physical location on the BIG-IP system.
5. Click Endpoint Settings from the left pane. The Artifact Resolution Service list displays.
   1. From the Artifact Resolution Service list, select an artifact resolution service that you created earlier. If you do not have an artifact resolution service or you need to create a new artifact resolution service, click Create.
6. Click Assertion Settings from the left pane. The applicable settings display.
   1. From the Assertion Subject Type list, select the type of subject for the IdP to authenticate.
   2. From the Assertion Subject Value list, select the name of a session variable. This variable, %{session.logon.last.username}, is generally applicable. Some session variables are applicable depending on the type of authentication that you use for your site.
   3. Select the Enable encryption of Subject check box to encrypt the subject. The Encryption Strength list becomes available.
   4. From the Encryption Strength list, select a value. Supported values are AES128, AES192, and AES256.
7. Click SAML Attributes from the left pane. The SAML Attributes list displays. For each attribute that you want to include in the attribute statement, repeat these substeps.
   1. Click Add.
   2. Type a name and a value in the new row. Usually, the name is a fixed string; it can be a session variable. You can use a session variable for the value. This example shows using a fixed string for the name and a session variable for the value. Name: user_telephonenumber and value: %{session.ad.last.attr.telephoneNumber}.
   3. Select the Encrypt check box and select a value from the Type list. Select the check box to encrypt the attribute. Supported values for type are AES128, AES192, and AES256.
   4. Click Update.
8. Click Security Settings from the left pane.
   1. From the This device's Assertion Signing Key list, select the key from the BIG-IP system store. None is selected by default.
   2. From the This device's Public Certificate list, select the certificate from the BIG-IP system store. When selected, the IdP (the BIG-IP system) publishes this certificate to the service provider so that the service provider can verify the assertion. None is selected by default.
9. Click OK. The popup screen closes. The new IdP service appears on the list.

1. On the Main tab, click Access Policy > SAML > BIG-IP as IdP. The BIG-IP as IdP screen displays a list of SAML IdP services.
2. Select a SAML IdP service from the table and click Export Metadata. A popup screen opens, with No selected on the Sign Metadata list.
3. For APM to sign the metadata, perform these steps:
   1. Select Yes from the Sign Metadata list.
   2. Select a key from the Signing Key list. APM uses the key to sign the metadata.
   3. Select a certificate from the Signature Verification Certificate list. APM exports the certificate to the metadata file. The system on which you import the metadata file can use the certificate to verify the metadata signature.
4. Select OK. APM downloads an XML file.

1. On the Main tab, click Access Policy > SAML > BIG-IP as IdP. The BIG-IP as IdP screen opens and displays a list of local IdP services.
2. On the menu bar, click External IdP Connectors. A list of SAML IdP connectors displays.
3. Select Create > From Metadata. The Create New SAML IdP Connector screen opens.
4. In the Select File field, browse to and select the metadata file for the IdP.
5. In the Identity Provider Name field, type a unique name for the IdP.
6. If the metadata is signed, select a certificate from the Select Signing Certificate list.
7. Click OK. The file is uploaded, the SAML IdP connector is created, and the screen closes.

1. On the Main tab, click Local Traffic > Virtual Servers. The Virtual Server List screen opens.
2. Click the Create button. The New Virtual Server screen opens.
3. In the Name field, type a unique name for the virtual server.
4. In the Destination Address field, type the IP address for a host virtual server. This field accepts an address in CIDR format (IP address/prefix). However, when you type the complete IP address for a host, you do not need to type a prefix after the address.
5. In the Service Port field, type 443 or select HTTPS from the list.
6. For the HTTP Profile setting, verify that the default HTTP profile, http, is selected.
7. For the SSL Profile (Client) setting, from the Available list, select the name of the Client SSL profile you previously created, and using the Move button, move the name to the Selected list.
8. For the SSL Profile (Server) setting, from the Available list, select the name of the Server SSL profile you previously created, and using the Move button, move the name to the Selected list.
9. Click Finished.

1. On the Main tab, click Access Policy > SAML > BIG-IP as IdP. The BIG-IP as IdP screen opens and displays a list of local IdP services.
2. Click Create. The Create New SAML SP Service screen opens.
3. In the Name field, type a unique name for the SAML SP service.
4. In the Entity ID field, type a unique identifier for the service provider that includes the URI that points to the virtual server you created for this BIG-IP system and a unique path. For example, if you type https://bigip-sp/sp, then https:/bigip-sp points to the virtual server on this BIG-IP system and "/sp" is a unique string.
   Note: The path is not a physical path on the BIG-IP system, but a string that distinguishes one SAML SP service from another when multiple SAML SP services are configured on this BIG-IP system.
5. In the Relay State field, type a scheme, host, and path. This is a path is where this BIG-IP system redirects users after they are authenticated.
6. From the left pane, select Security Settings. The screen changes to display the applicable settings.
   1. Select Signed Authentication Request if you want this BIG-IP system to send signed authentication requests to the SAML IdP.
   2. Select Want Encrypted Assertion if this BIG-IP system requires encrypted assertions from the SAML IdP.
   3. Select Want Signed Assertion if the BIG-IP service provider system requires signed assertions from the SAML IdP. This is selected by default. It is recommended that it be selected.
   4. From SP's Authentication Signing/Assertion Decryption Private Key, select a key from the BIG-IP system store on this device. You can select a private key only when you select at least one of these check boxes: Signed Authentication Request and Want Encrypted Assertion. APM uses this private key to sign the authentication request to the IdP and to decrypt an encrypted assertion from the IdP.
   5. From SP Certificate, select a certificate. APM includes this certificate in the SAML SP metadata that you export. After the SAML SP metadata is imported on the IdP, the IdP can use this certificate to verify a signed authentication request and to encrypt an assertion.
7. Click OK. The screen closes.

1. On the Main tab, click Access Policy > SAML > BIG-IP as IdP. The BIG-IP as IdP screen opens and displays a list of local IdP services.
2. Select a SAML SP service from the list.
3. Click Bind/Unbind IdP Connectors. A pop-up screen displays a list of any IdP connectors that are associated with this SP service.
4. Click Add New Row.
5. Select the SAML IdP connector for the BIG-IP system that acts as the IdP in the federation. Because you are binding only one IdP connector to the SP service, you do not need to fill in the Matching Source and Matching Value fields.
6. Click Update. The configuration is not saved until you click OK.
7. Click OK. APM saves the configuration. The screen closes.

1. On the Main tab, click Access Policy > SAML > BIG-IP as IdP. The BIG-IP as IdP screen opens and displays a list of local IdP services.
2. Select an SP service from the list and click Export Metadata. A popup window opens, displaying No on the Sign Metadata list.
3. For APM to sign the metadata, perform these steps:
   1. Select Yes from the Sign Metadata list.
   2. Select a key from the Signing Key list. APM uses the key to sign the metadata.
   3. Select a certificate from the Signature Verification Certificate list. APM exports the certificate to the metadata file. The system on which you import the metadata file can use the certificate to verify the metadata signature.
4. Select OK. APM downloads an XML file.

1. On the Main tab, click Access Policy > Access Profiles. The Access Profiles List screen opens.
2. In the Access Policy column, click the Edit link for the access profile you want to configure. The visual policy editor opens the access policy in a separate screen.
3. Click the (+) icon anywhere in the access policy to add a new action item.
   Note: Only an applicable subset of access policy items is available for selection in the visual policy editor for any access profile type.
   A popup screen opens, listing predefined actions on tabs such as General Purpose, Authentication, and so on.
4. On the Authentication tab, select SAML Auth and click the Add Item button. The SAML Auth properties window opens.
5. In the SAML Authentication SP area from the AAA Server list, select a SAML SP service and click Save. The Access Policy window displays.
6. Add any additional actions that you require to complete the policy.
7. Change the Successful rule branch from Deny to Allow and click the Save button.
8. At the top of the window, click the Apply Access Policy link to apply and activate your changes to this access policy.
9. Click the Close button to close the visual policy editor.

Simple access policy to authenticate users against an external SAML IdP

1. On the Main tab, click Local Traffic > Virtual Servers. The Virtual Server List screen opens.
2. Click the name of the virtual server you want to modify.
3. In the Access Policy area, from the Access Profile list, select the access profile that you configured earlier.
4. Click Update to save the changes.

1. On the Main tab, click Access Policy > SAML > BIG-IP as IdP. The BIG-IP as IdP screen displays a list of SAML IdP services.
2. On the menu bar, click External SP Connectors. A list of SAML SP connectors displays.
3. Select Create > From Metadata The Create New SAML Service Provider window opens.
4. In the Select File field, browse to and select the metadata file for the service provider.
5. In the Service Provider Name field, type a unique name for the service provider.
6. If the metadata is signed, select the certificate from the Select Signing Certificate list.
7. Click OK. The file is uploaded, the SAML SP connector is created, and the window closes.

1. On the Main tab, click Access Policy > SAML > BIG-IP as IdP. The BIG-IP as IdP screen displays a list of SAML IdP services.
2. Select a SAML IdP service from the list. A SAML IdP service provides authentication service.
3. Click Bind/Unbind SP Connectors. The screen displays a list of available SAML SP connectors.
4. Select the SAML SP connectors for the external BIG-IP systems that are configured as SPs and that you want to use this service.
5. Click OK. The screen closes.

1. On the Main tab, click Access Policy > Access Profiles. The Access Profiles List screen opens.
2. Click Create. The New Profile screen opens.
3. In the Name field, type a name for the access profile.
   Note: An access profile name must be unique among all access profile and any per-request policy names.
4. In the SSO Across Authentication Domains (Single Domain mode) area, from the SSO Configuration list, select the name of the local SAML IdP service.
5. In the Language Settings area, add and remove accepted languages, and set the default language. A browser uses the highest priority accepted language. If no browser language matches the accepted languages list, the browser uses the default language.
6. Click Finished.

1. On the Main tab, click Access Policy > Access Profiles. The Access Profiles List screen opens.
2. In the Access Policy column, click the Edit link for the access profile you want to configure. The visual policy editor opens the access policy in a separate screen.
3. Click the (+) icon anywhere in the access policy to add a new action item.
   Note: Only an applicable subset of access policy items is available for selection in the visual policy editor for any access profile type.
   A popup screen opens, listing predefined actions on tabs such as General Purpose, Authentication, and so on.
4. On the Logon tab, select Logon Page and click the Add Item button. The Logon Page Agent properties screen opens.
5. Make any changes that you require to the logon page properties and click Save. The properties screen closes and the visual policy editor displays.
6. Add one or more authentication checks on the fallback branch after the Logon Page action. Select the authentication checks that are appropriate for application access at your site.
7. Optional: Add any other branches and actions that you need to complete the access policy.
8. Change the Successful rule branch from Deny to Allow and click the Save button.
9. Click the Apply Access Policy link to apply and activate the changes to the access policy.
10. Click the Close button to close the visual policy editor.

Access policy to provide authentication for SAML service providers when this BIG-IP system is the IdP

1. On the Main tab, click Local Traffic > Virtual Servers. The Virtual Server List screen opens.
2. Click the name of the virtual server you want to modify.
3. In the Access Policy area, from the Access Profile list, select the access profile that you configured earlier.
4. Click Update to save the changes.