User manual NOVELL IFOLDER 3.6 ADMINISTRATION

[. . . ] novdocx (en) 24 March 2009 AUTHORIZED DOCUMENTATION Administration Guide Novell® iFolder® 3. 6 October 2009 www. novell. com OES2: Novell iFolder 3. 6 Administration Guide novdocx (en) 24 March 2009 Legal Notices Novell, Inc. , makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. , reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. , makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. , reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. [. . . ] These values have rational default settings and should only be changed if you are really sure of what you are doing. YaST displays the current settings for confirmation. 7. 6. 4 Exporting Self-Signed Certificates 1 Click Export drop-down and select Export to File. 2 Select Only the Certificate in PEM format. 4 Specify a filename for the certificate you have created and click Browse to find a loacation to save the file. 6 Convert the certificate in PEM format to DER format using OpenSSL command as given below: openssl x509 -in <certificate>. pem -inform PEM -out <certificate>. der -outform DER 7 Copy the certificate in DER format to the location you have configured for loading Recovery Agent Certificate during iFolder configuration. If the certificate is expired, you need to load the new certificates again to this location. For more information on this, see "Path to the Recovery Agent Certificates (optional):" on page 61. 8 Restart the iFolder server to load the Recovery agent certificates. Installing and Configuring iFolder Services 85 novdocx (en) 24 March 2009 7. 6. 5 Exporting Self-Signed Private Key Certificates For Key Recovery 1 Click Export drop-down and select Export to File. 2 Select Certificate and the Key in PKCS12 Format. This password is used with the certificate and the keys exported to a file in XML format. IMPORTANT: You must use a password different from the one you have used for certificate creation. 4 Specify a filename for the certificate you have created and click Browse to find a location to save the file. 5 Click OK to save the certificate. 7. 6. 6 Using KeyRecovery to Recover the Data Each iFolder has a unique data encryption key which is auto-generated during iFolder creation. The key is encrypted by using a passphrase provided by individual user and also by using the public key with the Recovery agent. If the user forget the secret passphrase, he or she cannot access either the iFolder data or the encrypted key used for recovering it unless the passphrase is saved locally (enabling Remember passphrase). To avoid this problem, user export the keys using the Security > Export Keys option in the client and send it manually to the Recovery agent using the e-mail address provided in the Export dialog box in the client GUI. The Recovery agent retrieves the keys and sends back to the user through e-mail or any other communication channel. It is recommended to save the file as <filename>. xml This section help you understand the process followed by a Recovery agent to retrieve the key. 1 Go to the location where iFolder is installed. 86 OES2: Novell iFolder 3. 6 Administration Guide novdocx (en) 24 March 2009 Platorm Default Location of the Utility Linux Windows /opt/novell/ifolder3/KeyRecovery C:/Program Files/iFolder/KeyRecovery. exe 2 Run KeyRecovery or KeyReovery. exe based on the platform you use and follow the onscreen instructions. The following table summarizes the decisions you make. Parameters Description Encrypted Key file path Private Key Decrypted Key file path Private Key password Encrypt Result key One time passphrase Specify the path (including the file name of the encrypted key ) for reading the encrypted keys. Specify whether you want to encrypt the decrypted key with one time passphrase. Default value: Yes Specify a one time passphrase to encrypt the decrypted keys. 3 Send the decrypted key usually by replying to the mail attached with the encrypted keys and the one-time passphrase (if the key is encrypted using the one-time passphrase) to the user. 4 Send the one-time passphrase (if the key is encrypted using the one-time passphrase) to the user through any other communication channel other than the one you used to exchange the key files. 7. 7 Accessing iManager and the Novell iFolder Web Admin The Novell iFolder Web Admin is the tool used to manage your iFolder server. 1 Open a Web browser to the iManager Login page by entering the following location: http://servername. example. com/nps/iManager. html Replace servername. example. com with the DNS name or IP address (such as 192. 168. 1. 1) of the OES Linux server where you installed iManager. This might be the same or different computer where you installed iFolder 3. 6 or iFolder 3. 6 Web Access. [. . . ] For more information on the Recovery Agent, refer to the Section 7. 2. 3, "Loading Recovery Agent Certificates in The iFolder Server, " on page 73. F. 2 Using Novell iFolder Server to Serve Large Files Novell iFolder is capable of serving large files, subject to the system or file system limits. However, Mono® has a race condition in the Mono version that ships with OES 2 that prevents large file uploads. The Mono team has fixed this issue in 1. 2. 5 release and the patch that contains all the Mono components, including XSP is available through the Novell Customer center. Ensure that you apply the patch before you start using iFolder for serving large file uploads. To apply the patch, ensure that, You complete the Novell Customer Center System Registration Procedure. [. . . ]