Configuring Active Directory with AD FS and SAML for Brainloop Secure Dataroom Copyright Brainloop AG, 2004-2015. All rights reserved. Document version 1.0 All trademarks referred to in this document are the property of their respective owners.
Content 1 Introduction... 3 2 Add Relying Party Trust... 3 3 Create Claim Rules... 9 4 Add SAML Logout... 12 5 Appendix: Document revision history... 14 Page 2 of 14
1 Introduction This setup guide is intended for system administrators configuring Active Directory with AD FS (Active Directory Federation Services) and SAML for use with Brainloop Secure Dataroom. For information on setting up SAML authentication in Brainloop Secure Dataroom, please refer to our SAML setup and user guide Configuring SAML Authentication for Brainloop Secure Dataroom. 2 Add Relying Party Trust 1. Start AD FS Management. 2. Select the Relying Party Trusts folder from AD FS Management. 3. Add a new Standard Relying Party Trust from the Actions sidebar. This starts the configuration wizard for a new trust. 4. In the Welcome screen, click Start. 5. In the Select Data Source screen, select the last option, Enter data about the party manually. Page 3 of 14
6. In the Specify Display Name screen, enter a Display name that you recognize in the future and any notes you want to make, then click Next. Page 4 of 14
7. In the Choose Profile screen, select the AD FS profile option and click Next. 8. In the Configure Certificate screen, leave the certificate settings at their defaults and click Next. Page 5 of 14
9. In the Configure URL screen, enable the Enable support for the SAML 2.0 WebSSO protocol option. As the service URL, enter https://my.brainloop.net/newlogin/saml.aspx (or replace my.brainloop.net with your server domain) and click Next. 10. In the Configure Identifiers screen, in the Relying party trust identifier field, enter https://my.brainloop.net/ (or replace my.brainloop.net with your server domain), click Add, then Next. Page 6 of 14
11. In the Configure Multi-factor Authentication Now screen, select the I do not want to configure multi-factor authentication settings for this relying party trust at this time option and click Next. 12. In the Choose Issuance Authorization Rules screen, select the Permit all users to access this relying party option and click Next. Page 7 of 14
13. In the Ready to Add Trust screen, an overview of your settings is displayed. Click Next. 14. In the Finish screen, click the Close button to exit and open the Claim Rules editor. Page 8 of 14
3 Create Claim Rules 1. Once you have completed all the steps described in the previous chapter, the Edit Claim Rules editor is displayed: 2. Click Add Rule. 3. Select the Send LDAP Attributes as Claims template and click Next. Page 9 of 14
4. In the Configure Claim Rule screen, enter a Claim rule name and select Active Directory as your Attribute store. 5. Next, make the following settings: - In the LDAP Attribute column, select E-Mail Addresses. - In the Outgoing Claim Type column, select E-Mail Address. 6. Click Finish. 7. Now, create another new rule by clicking Add Rule, this time selecting Transform an Incoming Claim as the template. Page 10 of 14
8. In the Configure Claim Rule screen, enter a Claim rule name and make the following settings: - Incoming claim type: select E-Mail Address - Outgoing claim type: select Name ID - Outgoing name ID format: select Email - Leave the default rule Pass through all claim values enabled. 9. Click Finish. 10. In the Edit Claim Rules dialog, click OK. Page 11 of 14
4 Add SAML Logout 1. From the Actions sidebar or from the context menu on the created Relying Party Trust, select Properties. 2. Click Add SAML. Page 12 of 14
3. Make the following settings: - Endpoint type: select SAML Logout - Binding: select POST - Trusted URL: type https://my.brainloop.com/newlogin/singlesingout.aspx 4. Click OK. 5. Confirm your changes by clicking OK in the properties dialog. IMPORTANT: In order to be able to log in with SAML, e-mail addresses for users must be defined. Page 13 of 14
5 Appendix: Document revision history Version Date of change Revision 1.0 8 October 2015 First release Page 14 of 14