Release Notes Date: September 2013

Transcription

1 Release Notes Date: September 2013

2 All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means, or stored in any retrieval system of any nature without the prior written permission of Sunrise Software Limited, except for permitted fair dealing under the Copyright, Designs and Patents Act Sunrise Software Limited, Sostenuto is a registered trade mark of Sunrise Software Limited. Sunrise Software Limited does not assume or accept any liability for any loss or damage of any kind to any person that may arise as a result of that person (or any other person) using this document or acting or refraining from action in reliance on any information (including expressions of opinion) contained in this document. This limitation/exclusion of liability does not apply in the case of death or personal injury caused by negligence on the part of Sunrise Software Limited, or to the extent (if any) that a limitations and/or exclusion in these terms is not permitted under applicable law. Sunrise 50 Barwell Business Park Leatherhead Road Chessington Surrey KT9 2NY United Kingdom Visit us at Enquiries e: welcome@sunrisesoftware.co.uk t: +44(0) Page 2 of 13

3 C O N T E N T S Introduction 4 Note for Sostenuto 4.0 Users 4 Hardware and Software Requirements 4 Known Deviations/Errors 4 Release Features in Sostenuto Encryption 4 Forgotten Password 5 Deploying Sostenuto Obtaining the Installation Media 7 Migration from Sostenuto 4.1 and above 7 Migration Procedure 7 Migrating an existing Sostenuto Database 8 Chameleon jar Files 9 After Migration 10 Update the JRE on Each Client Machine 10 Re-installing Web Start 10 Apache HTTP Server Settings 11 Corrections 13 Page 3 of 13

4 Introduction These Release Notes detail the changes and corrections available in Sostenuto Sostenuto includes two specific changes to improve account security and lessen the likelihood of account passwords being hacked. Specifically these changes include: Change of Sostenuto Account password encryption to a non-reversible type. Changes to the Forgotten Password feature of Sostenuto, Iguana, Sostenuto Mobile and Chameleon. Note that you must have Iguana and Mobile installed to use this feature. Sostenuto is available both as a new installation and as a patch to existing installations. You can migrate to Sostenuto from Sostenuto 4.0 or any later Releases. If your current version of Sostenuto is earlier than 4.0, you must migrate to Sostenuto 4.0 before upgrading to Sostenuto For information about upgrading from earlier versions of Sostenuto, please contact the Sunrise Service Desk. Note for Sostenuto 4.0 Users Sostenuto 4.1 is designed to run from within the Apache Tomcat Server and not, as previously, from the Sun Java System Application Server Platform. This means that you cannot upgrade the existing version of Sostenuto in the same folder. Instead, Sostenuto 4.1 will be installed into a different directory. Note: Do not follow the Sostenuto Installation Guide instructions for migrating the Sostenuto database (pages 23-24). Instead follow the instructions on page 8 of these Release Notes for Migrating an existing Sostenuto Database. This will migrate your database from release 4.0 to Release in one step. Hardware and Software Requirements Hardware and software requirements vary depending on your deployment. See the Sostenuto ITSM Hardware and Software Configuration Guide for the specifications for your particular environment. Known Deviations/Errors All the issues outstanding on Sostenuto are still outstanding, except those listed in the Corrections at the end of the Release Notes. Release Features in Sostenuto All the features in Sostenuto 4.1+ are also available in this Release. Encryption Sostenuto now uses a SHA-2 non-reversible encryption algorithm. After upgrading to Sostenuto you must run a migration process on the Sostenuto database to update the database and any accounts to the new encryption type. This migration tool is provided with Sostenuto This encryption type will be the standard encryption with all future versions of Sostenuto, including the forthcoming Sostenuto 4.5. Page 4 of 13

5 Forgotten Password All Sostenuto interfaces, that is the Sostenuto JRE applet, Chameleon, Iguana and Mobile, now include a common Forgotten Password? link. This link leads to a page that allows the user to request a password reset by entering their configured Sostenuto username (as per the defined Account Profile configuration in Sostenuto). Note: While the screenshot above displays the input field as Account Name / Address, this can be changed depending on the configuration of the Account Profile. Different customer Sostenuto implementations can use different fields as the user s account name. In addition, the text displayed on each of the forms can be changed by editing the appropriate entries contained within the messages_en.properties file found in the classes\resources\common folder of the Sostenuto instance. Once the user has entered their Account Name, an containing a password reset link is sent to the address associated with the account and a confirmation is displayed. The content of the sent to the user is configurable. Figure 1: Requesting a Password Reset Clicking the link within the launches a new window, allowing the user to specify a new password. This link can only be used once, and expires after three days. Should the link expire, the user will need to follow the forgotten password process once again. The length of time that the password reset link will remain active is specified in the password-config.xml file located in the classes\settings\sostenuto folder of the Sostenuto instance. For example, the default is: <expiry-duration unit="days">3</expiry-duration> However, this can be changed to HOURS or even MINUTES if required and an appropriate value specified, for example: or <expiry-duration unit="hours">12</expiry-duration> <expiry-duration unit="minutes">60</expiry-duration> Page 5 of 13

6 To ensure high security, the generated password reset link is highly unique and cannot be guessed. An example can be seen below: EFh71IZDVaS6AswkBMsNxig5ipFH4jEYe962hBhXhqMtP%2B%2FIxXT2KPm6DgS47zhLxUk d28qrulvlvn5zjnq7tpyvh4gygfvogvu7fvudyklwewczhcoxkqzzgefa%2bowbmwmiu 57dIccSZK13K5g8cciOEHdz%2FMiJ0CmGwBrllLhyqwi8tqCO47KH%2Fqw8X%2ByujkC9tsV FHkOcbuaRh%2BbwfX5EDBa4EcJ5BXsmUba6ZgcIOWpOPERUmI1G7fUycwV8qGuJf9NSe w1djn1nteunacpst29qzbr9buamgdjypsxweav4buebjvd8qnup91zttukmhksqhxa7q N0IZyTNXa3wwtE%2BKcEXrJrvmbczSaKzdxMBX3dfOs0n%2FOr8daEsX3pCGXKMidAJ7Tf8 15xHtBwdoOTxparwnaDzDxW96nBIHzLUKYV1Q%2B1koqFlCBOpDGqeJLY8YN%2F0mNNJ u2ucadutztprb0kt8fwduczn1rqaj2xf1b8drz5kchdf%2b08dedvqk1zgbo8armpzp5 oz%2bhkqlnttvcyu5cv04tkzckzui9gsfik1i3ej3jw%3d%3d In the received by the user, the link can be included as part of hyperlink text, i.e. Click here to reset your password. You can configure the contents of the by editing the forgot-password- _en.txt file in the classes\resources\common folder of the Sostenuto instance. The text supports HTML tags so there is additional control over the look of the if corporate branding is required. The reset password screen can contain an optional challenge field that must be entered alongside the new password in order for the change to be successful. In the following screenshot the challenge question requires the user to confirm the address of the account, but this can be changed to any other Sostenuto field within the account s parent Service. The field used for the challenge question is identified in the <question_fieldid>field ID</question_fieldId> section of the classes\settings\sostenuto\password-config.xml file of the Sostenuto instance. To edit the challenge question, update the <question_fieldid>field ID</question_fieldId> with the FIELDID that you want to use. The user is also required to enter their password twice to ensure no mistypes. An indicator next to the password field shows the relative strengths of the new password. The current version of Sostenuto does not enforce password strength via policy as yet, but it is hoped that including the indicator will educate users as to what is an acceptable password. On click of the Reset Password button, the password for that account will be changed provided that: the challenge question is correct the entered passwords both match the password is not blocked by Sostenuto password history tracking. The user can then navigate back to the login page they came from and log in with the new password. Page 6 of 13

7 Deploying Sostenuto Obtaining the Installation Media Sostenuto is available to download from Sunrise Software Ltd. To obtain the Sostenuto installation media please contact the Sunrise Service Desk for a URL. T: +44 (0) E: support@sunrisesoftware.co.uk Using the URL provided, download the Sostenuto Migration from or above folder from the website and save it locally. Migration from Sostenuto 4.1 and above Sostenuto will be available both as a new installation and as a patch to existing 4.1.x installations. The password encryption utility will be updated when you migrate the Sostenuto database. You are recommended to back up the database before running this utility. The Sostenuto Migration from or above folder contains all the.jar and.js files for updating Chameleon, to correct the update issues for users who access Chameleon with SSO. Notes Users migrating from Sostenuto 4.1 will now be able to use the PSN validation feature, which was added in Release PSN validation is added to the ticketing mechanism to ensure that you only access the correct Sostenuto database via SSO. A new property at the end of the server.properties file enables you to set PSN validation on or off. The password encryption feature is available to Iguana and Sostenuto Mobile users who have installed Iguana and Mobile Migration Procedure To migrate from Sostenuto 4.1+ to Sostenuto 4.1.3: 1 Stop the Apache Tomcat Services. 1 Back up the current Sostenuto home directory and the Sostenuto database. 2 Open the Sostenuto Migration from or above\installation folder. 3 To upgrade your Sostenuto application, extract the 03-sostenuto-tomcat-webapps.zip file into C:\Program Files (x86)\apache Software Foundation\Tomcat 7.0\webapps\[Sostenuto application] to update the Sostenuto files. 4 The migration process replaces the server.properties file in \[Sostenuto Application]\WEB- INF\classes\settings\sostenuto. If you have migrated from Sostenuto or above, you can replace the updated file with the one from your backup. If you have migrated from Sostenuto 4.1.0, please compare the new file with your backup and re-enter any missing information, particularly the DBServer and Password information. 5 The migration process also replaces the web.xml file in \[Sostenuto Application]\WEB-INF. If you have Iguana or Mobile, you will need to uncomment these sections again. If you have any extra access points (for Customers or Third parties etc.), you will need to add them again. Please do not replace the file with your backup as there are new options included within the upgraded file. Page 7 of 13

8 Migrating an existing Sostenuto Database Existing Sostenuto 4.1.x database versions are required to be migrated to the latest version. To complete the migration of the database, follow the steps below. 1 Ensure that the <docrootpath>\setenv.bat file shows the Java path, Sostenuto installation path and the Sostenuto web app name. 2 If you are configuring Sostenuto for NT authentication and didn t log in as the desired user account (the account to be used for NT authentication), right-click on the migration.bat file to see the context menu shown below. Specify the credentials of the desired user account and click OK. 3 Execute the migration.bat file. The migration log can be viewed in the location specified in the log4j.properties file. 4 Restart the Apache Tomcat Services. Note that the migration process clears the existing password tracking history data. 5 If your installation is configured for Single Sign On (SSO) or load-balancing, check the contents of the httpd.conf.file. See Apache HTTP Server Settings on page 11. Page 8 of 13

9 Chameleon jar Files In your previous build of Sostenuto, style sheets may have been changed to alter the colours and images displayed within Chameleon. Copy the following folders and files from the Sostenuto backup to the Sostenuto installation to restore the Chameleon look to your customised settings. <docrootpath>\resources\chameleon\images <docrootpath>\resources\chameleon\css\en\chameleon.css Next, run the Chameleon compile.bat file for the fix to take effect. This generates the HTML folder containing the JSP files. For more information on compiling Chameleon please refer to the Chameleon Configuration Guide. When the HTML folder has been recreated, copy the custom JSP files from the Sostenuto backup folder into the <docrootpath>\web-inf\jsp\chameleon\templates\en folder where any custom JSPs have been added. Please refer to your consultancy documentation for details of any JSP files that have been altered. Page 9 of 13

10 1. After Migration Update the JRE on Each Client Machine Sostenuto can only run on client machines which have the correct JRE installed. If the correct JRE is not present on a client machine, a prompt similar to this will be displayed when you attempt to run Sostenuto: Click one of the Allow options to continue. Re-installing Web Start If the Sostenuto client is being accessed via Web Start, this must be uninstalled and re-installed to work with the updated version of Sostenuto Please refer to the Sostenuto Installation Guide for details of installing Web Start. Page 10 of 13

11 Apache HTTP Server Settings Read the following information if your system is configured for SSO and/or load balancing. A detailed explanation of all the settings can be found in the Load Balancer Configuration section of the Sostenuto Installation Guide. The final part of the Apache Software Foundation\Apache2.2\conf\httpd.conf file must contain the settings for load-balancing, SSO and Proxy servers. If any of the code is missing, copy and paste it from this document in the order it appears here, then edit it as explained below. Load-balancing settings: ProxyRequests off ProxyPass / balancer://mybalancer/ stickysession=jsessionid scolonpathdelim=on ProxyPassReverse / balancer://mybalancer/ <Proxy balancer://mybalancer > BalancerMember route=tomcata loadfactor=100 </Proxy> SSO settings: <Location /Sostenuto > # Order allow,deny # Allow from all SetEnv proxy-chain-auth On Require valid-user AuthType SSPI AuthName "Windows Authentication" SSPIAuth On SSPIAuthoritative On SSPIDomain DOMAIN NAME SSPIOmitDomain On SSPIOfferBasic Off SSPIUsernameCase lower Proxy server settings: RewriteEngine On RewriteCond %{SERVER_NAME} (.+) RewriteRule. - [E=SERVER_NAME:%1] RewriteCond %{SERVER_PORT} (.+) RewriteRule. - [E=SERVER_PORT:%1] RequestHeader set X-Remote-Address %{SERVER_NAME}e:%{SERVER_PORT}e" </Location> RequestHeader set X-PSN Remote User s PSN RewriteCond %{LA-U:REMOTE_USER} (.+) RewriteRule. - [E=RU:%1,NS] RequestHeader set X-Forwarded-User %{RU}e RewriteCond %{LA-U:HTTPS} (.+) RewriteRule. - [E=RP:%1,NS] RequestHeader set X-Forwarded-Https %{RP}e Load-balancing settings These settings are needed for load balancing. They are ignored until the load-balanced parameter in the server.properties file is set to true. If you are using load-balancing, ensure that route= is set to the ID of your Tomcat server, shown in red above. Page 11 of 13

12 SSO settings Enter the SSO settings that are appropriate for your installation. If SSO is enabled, keep all the SSO settings and enter your domain name at SSPIDomain, as shown above. If SSO is NOT enabled, keep the first three lines and remove the comments then delete all the following SSPI settings, as shown below: <Location /Sostenuto > Order allow,deny Allow from all Proxy server settings These settings are used in conjunction with the load-balancing settings above to rewrite the server address with the address of the remote user s proxy server, before sending it to the user. They should be present even if you do not have load-balancing. If you have load-balancing, enter the Remote User s PSN as shown above. Page 12 of 13

13 Corrections This section details the corrections that have been included in this release. Issue No.: PRB Summary: When Encountered: Description Sostenuto to store passwords using one-way hash encryption. Sostenuto should be able to store passwords in one-way hash encryption, rather than reversible encryption as is currently configured. This also means that the Forgotten Password link would need to be configured with a verified password reset rather than being ed in plain text. Page 13 of 13