Web Federated Login (SAML) with inotes & Integrated Windows Authentication Open Mic May 21, 2014

Transcription

1 Web Federated Login (SAML) with inotes & Integrated Windows Authentication Open Mic May 21, 2014 Yvonne Devlin, Software Engineer IBM Collaboration Solutions Powered by IBM SmartCloud Meetings 2014 IBM Corporation

2 Aim: To discuss the detailed implementation of Web Federated Login and Integrated Windows Authentication IBM Corporation

3 Advantages of using SAML(Security Assertion Markup Language) Reduces Administrative costs for maintaining passwords Increased security by using cryptographic mechanisms instead of passwords password info is unavailable to hackers to launch an offline password guessing attack Less password prompts for your users One SSO approach for countless different products IBM Corporation

4 How is SSO possible across third party applications with SAML? User's identity is represented in a signed XML assertion. User may be known to applications across domains and across corporations. Usually the SAML(XML) assertion contains the user's address. A service (Domino / WAS) receives the user's identity assertion. The assertion must pass cryptographic verification. The service doesn't need the user's password to know who the user is IBM Corporation

5 SAML Federated Identity architecture SAML Identity Provider (IdP) Server creating the SAML assertion Service Provider (SP), for example, Domino 9.x Server processing the SAML assertion Clients used for accessing services Browser IBM Corporation

6 Supported IDPs Microsoft ADFS 2.0 integrated with Active Directory IBM Tivoli Federated Identity Manager (TFIM, IBM Security Identity Manager) Its possible to use other implementations of IdPs but they are currently not supported IBM Corporation

7 Web Federated Login requires four components 1)A Web browser client for all inotes users 2)Domino Web server running inotes and functioning as the home (mail) server for inotes client users 3)Domino ID vault server 4)SAML Identity Provider (IdP) IBM Corporation

8 Checks to be completed before implementing Web Federated Login with inotes If using ADFS or implementing SSL with TFIM then confirm that you can access your server through HTTPs Confirm your inotes user has been added to the vault and can access their ID for encrypting/decrypting mails Confirm your inotes user can authenticate with your inotes server using web authentication with SAML IBM Corporation

9 Domino web server authentication using SAML IBM Corporation

10 Web federated login IBM Corporation

11 Setting up Web Federated Login The documentation assumes that the Inotes Server and the Vault server are two different servers. The idpcat.nsf and a configuration document needs to be set up on both servers. The idpcat.nsf is where you provide Domino with the details of your IDP If the ID vault server is separate, it does not need to have SSL enabled Even if the inotes Server and the Vault server are the same server, two separate configurations need to be implemented in the idpcat.nsf IBM Corporation

12 Creating a configuration document in the idpcat.nsf database The database idpcat.nsf is not created by default.it can be created from the idpcat.ntf template. You must use the name idpcat.nsf. If using unix the filename must be all lower case The Admin creating the document must be listed in the following fields on the server Full Access Administrators Administrators Sign or run unrestricted methods and operations. The idpcat.nsf must not be enabled for document locking. If using the Create button to generate a certificate to use with SAML then the server ID cannot have a password IBM Corporation

13 Creating a configuration document in the idpcat.nsf database cont.d The IdP Catalog application (idpcat.nsf) must exist on the Domino server that hosts the ID vault whether or not that is the same computer that runs inotes. You will always have two IdP config documents for any inotes server supporting Web Federated Login. One IdP config document is for the inotes server with SAML authentication, and this document must reside in the IdP Catalog application on the inotes server. The second IdP config document is for the inotes server interface with the ID vault, and this document must reside in the IdP Catalog application on the ID vault server. The documents are similar, but differ in a few important fields IBM Corporation

14 inotes configuration document in idpcat.nsf Hostname is the URL your inotes user uses to access their home mail server Also you need to list the IP address associated with your SSL configuration The Service provider ID is the string that identifies Domino as a SP partner with the IdP IBM Corporation

15 inotes configuration document in idpcat.nsf cont.d For company name specify any string that is convenient for your administrators Domino pre-pends "CN=" to the string in the Company name field and uses this name as the certificate subject. When you click on create certificate it creates a certificate and adds it to your server ID It also adds the certificate public hash value to your configuration IBM Corporation

16 inotes configuration document in idpcat.nsf cont.d In the Domino URL field, enter a string to identify the fully qualified DNS name of the inotes server. The string in this field is used by the IdP as the initial part of the URL for sending the user's SAML assertion back to Domino. You can use the string you entered in the Service Provider ID field on the Basics tab. While not supported with Domino the Single logout URL is a requirement if using TFIM. Enter a syntactically correct URL expected by the IdP IBM Corporation

17 inotes configuration on the IdP Use the URL for accessing your inotes server with /names.nsf?samllogin appended IBM Corporation

18 inotes configuration on the IdP cont.d The string entered into the Relying party trust identifier field needs to needs to match the value in the Service Provider ID field located in the Domino idpcat configuration document IBM Corporation

19 inotes server interface with the ID vault second config document Enter a virtual name for the inotes interface to the vault on the Basics tab The resulting hostname does not need to be defined in DNS. If the ID vault is on a server that is configured for HTTP/HTTPS, you should not include an IP address. For the Service Provider ID field the string should be a syntactically-correct URL, as if the virtual hostname would be featured in a URL IBM Corporation

20 inotes server interface with the ID vault second config document cont.d With the Domino URL field for the inotes server interface with the ID vault, the instructions are the same as the previous config document, except to note that the Domino URL will not be the same string as you entered in the Service Provider ID field on the Basics tab. Use the hostname for the inotes server instead of the virtual hostname. This is the hostname the IdP uses to return the SAML assertion so it needs to be a hostname that can be resolved by your DNS IBM Corporation

21 ID vault config on the IdP Use the inotes URL configured in your DNS With this config however you append /names.nsf?samlidlogin IBM Corporation

22 ID vault config on the IdP cont.d As before the string entered into the Relying party trust identifier field needs to match the value in the Service Provider ID field located in the Domino idpcat configuration document In this case its the virtual hostname we used for the vault configuration that is entered here IBM Corporation

23 Configuring the ID vault for Web Federated Login The ID vault administrator must approve the use of an IdP that will provide SAML credentials. The administrator supplies host names for identity provider (IdP) partnerships to the ID vault in a vault document. The vault server uses the host names to look up IdP information from the idpcat.nsf IBM Corporation

24 Using a security settings policy to apply a Web Federated Login configuration to your inotes users Before you can apply the policy to support Federated Login, you also need to export a copy of the Internet SSL certificate from your federation (ADFS or TFIM 2.0), Import that certifier into your Domino Directory Create an internet cross certificate IBM Corporation

25 Using a security settings policy to apply a Web Federated Login configuration to your inotes users cont.d Open the existing Security Settings policy for users of your organization s ID vault. Select the Password Management -> Federated Login tab. Select Yes for Enable Web federated login with SAML IdP. Select Set value whenever modified for how to apply this setting. For inotes deployments that have been upgraded to the current release, when the policy is initially being deployed, select Additional settings for Federated Login (Notes or Web) Allow password authentication with the ID vault Yes IBM Corporation

26 Integrated Windows Authentication (IWA) IWA is not necessary for SAML configuration Stops an inotes user from being prompted for a password once they log on to their machine IBM Corporation

27 The following need to be in the same Windows Active Directory domain ADFS server Client computer where the user is logging into Windows and running the browser or Notes client The record for the user who is being authenticated via IWA IBM Corporation

28 Step 1: Create the ADFS Kerberos identity The Windows administrator logged into the Windows domain creates the ADFS Kerberos identity. This identity must be mapped to the Active Directory user that represents the ADFS HTTP server instance. setspn -a HTTP/dublcsvm20.saml.domino.com dublcsvm20$ setspn -a HTTP/dublcsvm20 adfs01$ IBM Corporation

29 Step 2: Set up the browser for the Windows client inotes user The settings discussed are from Internet Explorer Under Internet Options Advanced ensure that Enable Integrated Windows Authentication is selected Under Internet Options Security Local Intranet select Automatic logon only in Intranet Zone IBM Corporation

30 Step 2: Set up the browser for the Windows client inotes user con.d Under Internet Options Local Intranet Sites add your ADFS URL IBM Corporation

31 Related Links Supporting federated login on the inotes client lotus.com/ldd/dominowiki.nsf/xpDocViewer.xsp? lookupname=administering+ibm+inotes social+edition#action=op endocument&res_title=supporting_federated_login_on_the_inotes_client_ in901&content=pdcontent Cookbook: Setting up ADFS for integrated Windows authentication (IWA) lotus.com/ldd/dominowiki.nsf/dx/Cookbookcol_Setting_up_ADFS_for_in tegrated_windows_authentication_lpriwarpr_ Supplementary information on Security Assertion Markup Language (SAML) configuration combinations of IBM Domino and other products IBM Corporation

32 Press *1 on your telephone to ask a question. Visit our Support Technical Exchange page or our Facebook page for details on future events. To help shape the future of IBM software, take this quality survey and share your opinion of IBM software used within your organization: IBM Collaboration Solutions Support page IBM Collaboration Solutions Support IBM Corporation