Configure SmartForms for Active Directory Federation Services (AD FS)

Configuring SmartForms to work with AD FS requires that your SmartForms site is enabled for SSL.

1. Open Internet Information Services (IIS) Manager.
2. In this example the product site is used. Right - click the K2 site and select Edit Bindings.
   

3. Click Add.
4. Select https from the Type drop down list and type a new number into the Port field.
5. Select the certificate used for your site. In this example it is the *.denallix.com April 2015 Certificate, which was purchased from a valid Certificate Authority.
   When working with systems like AD FS that are internal to the organization, Self-signed and Domain Certificates can work in place of purchased certificates. If you plan to also integrate with an online system like Azure Active Directory you will need to use a purchased certificate.
   
   
   
6. To make sure that the new HTTPS configuration is updated properly in the configuration, rerun the Setup Manager.

The Token-signing certificate from AD FS must be installed in the Trusted Root Certification Authorities location on the server.

1. Open the AD FS Management Console.
2. Expand the Service Node.
3. Select the Certificates Node.
4. Right-click the Token-signing certificate and select View Certificate.
   
5. Select the Details tab and click Copy to File.
   
6. Walk through the Certificate Export Wizard, creating a DER encoded binary X.509 certificate file.
7. Copy the .CER file to the K2 server.
8. On the product server double-click the .CER file and click Install Certificate on the General Tab.
   
9. Select Place all certificates in the following store on the Certificate Import Wizard and choose the Trusted Root Certificate Authorities store.
   
10. Click OK, Next and then Finish to complete the wizard.

In order for the system to authenticate the users from Active Directory Foundation Services, you must configure a Trusted LDAP Security Provider against a custom security label, for example, ADFS. You can configure the Trusted LDAP Security Provider by following the steps in the Configuring the K2 LDAP User Manager.

A Claim Issuer is required for the system to map the STS signing certificate with the security tokens.

1. Open the Management site and browse to Authentication > Claims > Issuers.
2. Click New.
3. Enter a Name and Description for the AD FS Issuer.
4. Enter the Token Issuer endpoint for AD FS in the Issuer textbox (Example: http://adfs.denallix.com/adfs/services/trust).
5. Enter the Login URL for AD FS in the URI textbox (Example: https://adfs.denallix.com/adfs/ls/).
6. Enter the Thumbprint of the Token-signing certificate for AD FS.
   
   A system administrator can use the following Powershell command to print the thumbprint to screen. Copy and paste the result into the Thumbprint field of the New Claim Issuer dialog.
   Get-AdfsCertificate "Token-Signing" | Select-Object CertificateType, Thumbprint
7. Check the Use for Login check box and click OK to add the AD FS issuer.

Claim mappings are used to identify the incoming claims and map them to the appropriate security label.

1. Open the Management site and browse to Authentication > Claims > Claims.
2. Click New on the Security Label section, the New Claim Mapping page opens.
3. Select the Security Provider you configured in Step 3 from the Security Label drop down.
4. Select the Issuer you configured in Step 4 from the Issuer drop down.
5. For the Identity Provider Original Issuer textbox enter the Original Issuer value for AD FS (Example: http://adfs.denallix.com/adfs/services/trust)
6. For the Identity Provider Claim Type textbox enter the Claim Type value for AD FS. The recommended approach is to create a static claim using the following: http://schemas.microsoft.com/identity/claims/identityprovider
7. For the Identity Provider Claim Value textbox enter the Authentication Method Claim Value for AD FS (Example: urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport
8. For the Identity Original Issuer textbox enter the Original Issuer value for AD FS (Example: http://adfs.denallix.com/adfs/services/trust)
9. For the Identity Claim Type textbox enter the Claim Type value for AD FS (Example: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name)
10. Leave the Identity Claim Value textbox empty as this claim will be different for each user that logs in at runtime.
11. Click OK to add the mapping.

The values presented here are for example purposes only. Use the Original Issuer value for your AD FS environment, the Claim Type value for your AD FS environment, the Authentication Method Claim Value for your AD FS environment, the Original Issuer value for your AD FS environment, and the Claim Type value for your AD FS environment.

The Realm is the unique value that associates the SmartForms site with the claims authentication options. Audience URIs are the actual URLs that will be used to access the SmartForms site. Additional Audience URIs can be specified for a single Realm. For example if you use https://k2.denallix.com/Runtime and http://dlx:81/Runtime to access the SmartForms site you will need both URLs registered as Audience URIs.

1. Open the Management site and browse to Authentication > Claims > Realms.
2. The list of Realms should be pre-configured with your Runtime, Designer, and View Flow realms and Audience URIs. For each realm that you want to enable AD FS authentication for follow the steps below:

1. Select the desired Realm and click Edit.
2. In the Edit Realm dialog use the check box to select the desired issuers to map to the realm.
3. Click OK.

The following steps are required to add a relying party trust to the token issuer. This must be done for each site that was configured above.

1. Launch the AD FS Management console.
2. Expand the Trust Relationships node.
3. Right-click on the Relying Party Trusts node and select Add Relying Party Trust…
   
4. Click Start.
5. Select Enter data about the relying party manually and click Next.
   
6. Enter a display name and description and click Next.
   
7. Select AD FS profile and click Next.
   
8. Optionally specify a token encryption certificate. Since SSL is being used for the site it is not necessary to also encrypt the token unless desired. Click Next.
9. Check Enable support for the WS-Federation Passive protocol.
10. Enter the SmartForms site URL (Example: https://k2.denallix.com/Runtime/) for the site for which you are configuring the Relying Party Trust, and click Next.
    
    
    You must configure the product as a Relying Party in AD FS for each SmartForms site, especially when you have multiple design and runtime sites. The URL you specify here is carried forward to the Configure Identifiers page and must be unique. If you do not enter a URL on this page the Next button on the Configure Identifiers page is disabled.
11. Click Next on the Configure Identifiers page.
12. Click Next on the Multi-Factor authentication page.
13. Select the desired Issuance authorization rules option and click Next.
14. Click Next and Close.
15. The Edit Claim Rules dialog will open.
16. On the Issuance Transform Rules tab, click Add Rule…
    
    
17. Select Send LDAP Attributes as Claims and click Next.
    
18. Supply a name for the rule and select Active Directory as the Attribute store.
19. Configure the required and optional claim mappings:
    

    LDAP Attribute	Outgoing Claim Type
    SAM-Account-Name	Name
    Token-Groups – Unqualified Names	Role

    
    
20. Click Finish.
21. Click OK to complete the Claim Rule mappings.
22. Restart the product Host Server and navigate to a site that you configured for ADFS authentication. You may also need to clear your browser cache in order to clear any cached authentication.

If AD FS is the only authentication configured in the Realm to Issuer mapping then you should be redirected to the AD FS log in screen. If there are other authentication modes configured then you will see a page with a drop down that lets you select the authentication method that you want to use. Authentication that you have previously been using to access your smartforms sites will likely be cached by your browser. To enable you to login using AD FS you will first need to clear your browser cache.