Sentinel Cloud V.3.6 Release Notes

Transcription

1 Sentinel Cloud V.3.6 Release Notes

2 2 Sentinel Cloud V Release Notes Document Revision History Part number , Revision K May 2015 Disclaimer and Copyrights Copyright 2015, SafeNet, Inc. All rights reserved. We have attempted to make these documents complete, accurate, and useful, but we cannot guarantee them to be perfect. When we discover errors or omissions, or they are brought to our attention, we endeavor to correct them in succeeding releases of the product. SafeNet, Inc. is not responsible for any direct or indirect damages or loss of business resulting from inaccuracies or omissions contained herein. The specifications contained in this document are subject to change without notice. SafeNet and Sentinel are registered trademarks of SafeNet, Inc. All other product names referenced herein are trademarks or registered trademarks of their respective manufacturers.

3 Contents About This Document 4 Product Overview 4 Documentation Resources 4 Obtaining Support 4 What's New in This Release? 5 New EMS Admin Console 5 Named Entitlement Support (On-premise Entitlement Level) 5 Usage Data Management in Isolated Networks (On-premise) 6 Control License Use on Virtual Machines and Support Clone Protection 7 GUID Support in Customer Reference ID 7 Support for Sales Representative Address in EMS Web Services 8 New EMS Web Services 8 New EMS Reports 9 Enhancements in This Release 10 getinfo Scope and Format Aligned Across Cloud and On-premise Deployments 10 getinfo Scope Enhancement 10 Ability to Show or Hide Revoked Entitlements in EMS 11 Controlling Detach of a Lower Duration License 12 Maximum Detach Interval Increased 13 Feature Selection During Detach (On-premise Feature Level Deployment Mode) 13 Support for Feature Name Authorization in Cloud 13 Support for Feature Name Authorization in Cloud Connect Web Services 13 EMS Web Services Enhancements 13 Modified EMS Reports 14 Enhanced Proxy Support 14 Automatic Proxy Authentication for Run-time on Linux 14 Allow Running Multiple Application Instances 14 Installer Changes 14 Quartz Jar Renamed 14 Important Notes Related to Cloud Connect Web Services Version 15 Issues Fixed in This Release 16 Platforms Tested 19 Web Browsers Supported 21 Known Issues 22

4 4 Sentinel Cloud V Release Notes Sentinel Cloud V Release Notes About This Document This document contains information about the latest release of the Sentinel Cloud product, including new features, changes to the product, documentation, known issues and any workarounds. These release notes are subject to change. If you are reading the release notes that were available with the product's SDK, SafeNet recommends that you check the latest release notes available at the following location to see if any information was added or changed: Product Overview Sentinel Cloud Services is a feature-based user provisioning, authorization, metering, and management solution for software delivered as service or installed on customer s premises. For information about product and its components, refer to the Sentinel Cloud Run-time Guide, available at Documentation Resources Visit documentation.sentinelcloud.com to access the complete product documentation. Obtaining Support You can contact us by using any of the following options: Business Contacts - To find the nearest office or distributor, use the following URL: Technical Support - To obtain assistance in using SafeNet products, feel free to contact our Technical Support team: o o o Phone: (US toll free), (International) support@safenet-inc.com URL: Downloads - You can download installers and other updated components using this URL:

5 What's New in This Release? 5 What's New in This Release? This section describes the main features of Sentinel Cloud version 3.6. New EMS Admin Console The newly-introduced Admin Console in EMS is a centralized interface for managing server-side configurations. It provides flexibility to configure EMS and Cloud Connect settings as and when required, without requiring you to contact SafeNet Support. Admin Console is accessible only to administrators. To view Admin Console, login to EMS as administrator, and click Configure > Admin Console. Some of the management tasks that you can perform using Admin Console are : Configure on-premise licensing settings, such as detach interval, cache interval, virtual machine support, and clone protection. Specify range and default values of Time to Live (TTL) properties for postpaid and subscription license models. Control settings that determine how abandoned sessions are handled and concurrency is managed, such as session timeout and minimum usage count. Configure outgoing exchange server settings, such as SMTP host and port. Control the availability of entitlement certificate s, specify the intended recipients, and customize subject lines. Specify the technical support information to be mentioned in EMS s, such as team name and phone number. For more details, see EMS User's Guide, section "Admin Console". Named Entitlement Support (On-premise Entitlement Level) In the past, the named entitlements could be created only for the cloud applications. This release has extended this support to on-premise applications created with the Entitlement Level feature caching mode. In this case, you can limit the number of named users who can consume an onpremise entitlement. The number of named users can be specified during entitlement creation. The process of creating and reconfiguring on-premise named entitlements is same as that for cloud entitlements. For details, refer to EMS User's Guide and EMS Web Services Guide. Similarly the behavior of login and getinfo APIs in the case of on-premise named entitlements is now same as that for cloud entitlements. For details, refer to Run-time Guide. Limitations For on-premise deployment, the named entitlement support is limited to the Entitlement Level feature caching mode.

6 6 Sentinel Cloud V Release Notes Compatibility Information: To consume on-premise named entitlements (created with the Entitlement Level feature caching mode), you must upgrade the current implementation to the latest versions of Run-time (3.6) and Cloud Connect Web services (1.2). The old Run-times cannot consume named entitlements; they throw the internal error. Since change from named to unnamed (or vice versa) is not allowed during reconfiguration, the old entitlements (created with EMS versions older than 3.6) will remain unnamed. EMS and Cloud Connect Web services are backward compatible. Usage Data Management in Isolated Networks (On-premise) The support for isolated networks was introduced in the previous release, where licenses were allowed to be consumed on on-premise machines having no Internet connectivity. The usage data for isolated networks was collected but there was no provision to transfer that data to Cloud Connect. With this release, Run-time provides the ability to explicitly transfer usage data collected by isolated machines to Cloud Connect. This involves enhancing the transfer Run-time API to support a new action SYNC_USAGE_CUSTOM (32) and a new optional parameter for storing usage path. The usage data is collected for an entitlement only when the usage collection has been enabled in EMS during entitlement creation. To push usage data to Cloud Connect: 1. The usage data is transferred from an isolated machine to a connected machine (via USB dongle, intranet, or any other method), where it is placed in a desired folder. The usage folder should contain the following files: A master file with the name clientdetails. A usage file with the extension *.$$$. 2. From the connected machine, the transfer API is called with the following: The SYNC_USAGE_CUSTOM(32) action. An optional parameter containing the path of usage folder where the usage data is placed. For details, see Run-time Guide, section "Workflow for Isolated Machines". Limitation The usage of only one machine, for which the usage data is present at the specified location, can be sent to Cloud Connect at a time. Sub-folders, if any, are not considered. If you want to send usage data of multiple machines, you need to keep a separate usage folder for each machine.

7 What's New in This Release? 7 Control License Use on Virtual Machines and Support Clone Protection This release provides the ability to allow/disallow license use on virtual machines (VM), and enable protection against cloning to prevent license misuse. A software vendor can decide whether a feature should be accessible on virtual machines or not. In addition, you can prevent the consumption of license on an on-premise machine that has been detected as a clone. When clone protection is enabled, the existing licenses are forced to stop working. The cloned machine is treated as a new machine and machine registration is required for it to retrieve and use new licenses. EMS GUI Changes While adding products to a new or draft entitlement, two new check boxes are available: VM Enabled: Used to specify whether or not a protected application should run in virtualized environment. Clone Protection: Used to enable or disable protection against virtual machine cloning. Note that the Clone Protection setting is dependent on the VM Enabled setting. If VM Enabled is on, you can switch on/off Clone Protection. If VM Enabled is off, then Clone Protection is disabled. By using EMS Admin Console, you can specify the default behavior, that is whether the above two check boxes should be on or off by default. EMS Web Services New input optional parameters, cloneprotection and vmenabled have been added in the following web services: createentitlement, updateentitlement, searchentitlements, and getentitlementdetailsbyid. Refer to EMS Web Services Guide for details. Note The ability to control license use on virtual and cloned environments is available for onpremise Entitlement Level feature caching mode only. For on-premise Feature Level feature caching mode, both VM Enabled and Clone Protection settings are considered "on" always. GUID Support in Customer Reference ID Customer Ref ID identifies a customer uniquely in EMS and vendor's application. Earlier, it was either specified manually or generated by incrementing the last value of Customer Ref ID. Now, you can assign a random value called Globally Unique Identifier (GUID) to Customer Ref ID while creating new customers. The default value of Customer Ref ID Type can be configured by using the Admin Console. We recommend using GUID as the default because it randomizes Customer Ref IDs and thus provides security against misuse of licenses.

8 8 Sentinel Cloud V Release Notes Support for Sales Representative Address in EMS Web Services EMS web services now allow you to specify address of a person representing the software vendor, such as a sales representative, while creating or updating an entitlement. A new optional parameter alternate id has been introduced in createentitlement and updateentitlement web services to support this. Note: A sales representative's address can be associated to entitlements belonging to different customers. The entitlement certificate s are also sent to sales representative, if: o o s are enabled, that is, the Required field is set to Desired in EMS Admin Console. The value of Recipients is set to ISV or Both in EMS Admin Console. If notification rules are enabled, the notifications of an entitlement are also sent to the associated sales representative. New EMS Web Services The following table summarizes the EMS web services introduced in this release: Web Service retrievedetachdata getrawusagedataforcustomer Description Retrieves information of detached sessions for a customer, for the given dates. This web service is supported only for the Feature Level caching mode of onpremise entitlements. The data is reported for those sessions that have been detached after upgrading to Sentinel Cloud 3.6 back end. Retrieves raw usage data for a given entitlement of a customer for the given dates. This web service provides information of customer, entitlement, products, features, users, usagetype, vendor data, and client machine's host address. Related Section in EMS Web Services Guide Retrieve Detached Session Data Retrieve Customer Raw Usage Data

9 What's New in This Release? 9 Web Service Description Related Section in EMS Web Services Guide retrievefingerprintregistrationdetails Retrieves friendly name of a machine and EID registered to a fingerprint. searchcontacts Searches contacts for the given query parameters. Retrieve Fingerprint Registration Details Search Contacts New EMS Reports Following EMS reports have been introduced in this release: Report Raw Usage Data Report Peak Capacity Report Change Retrieves raw usage data for a given entitlement of a customer, for the given dates. This report provides information of customer, entitlement, products, features, users, usagetype, vendor data, and client machine's host address. This report functions similar to the getrawusagedataforcustomer web service of EMS. Determines the peak capacity of one/all postpaid feature(s) in a given duration across all entitlements of a customer. This report functions similar to the retrievepeakcapacity web service of EMS. For report details, see EMS User's Guide, section "Available Predefined Reports".

10 10 Sentinel Cloud V Release Notes Enhancements in This Release getinfo Scope and Format Aligned Across Cloud and On-premise Deployments The getinfo API has been enhanced so that similar scope and format can be used to retrieve information for on-premise and cloud deployments. The format types HIERARCHY_INFO and FEATURE_AUTHORIZATION that were available only for cloud are now supported for on-premise as well. With these format types: Note The getinfo API can provide hierarchical view of details available at various levels - entitlement, product, feature, and license attributes for on-premise deployments. The entitlement and product level details are also available for on-premise deployments, such as entitlement ID, time zone, product name, and product version. Earlier only the feature list was returned in the response of the getinfo API for on-premise deployments, but now the entitlement list is also returned which contains entitlement and product level details. Following additional details are retrieved at feature level for on-premise deployments: o o A Boolean value, IsDetachable, is retrieved to indicate if the feature can be detached or not. It is applicable for both Entitlement Level and Feature Level feature caching modes. A Boolean value, IsUsageEnabled, is retrieved to indicate if usage collection is enabled or disabled for the feature. It is applicable for Entitlement Level feature caching mode only. Following details are not retrieved at feature level for on-premise deployments: o o Upgrade Note Start date Notification information Independent software vendors (ISVs) who are using previous version of Run-time can continue to use the feature list to retrieve feature information for on-premise deployments. To use the entitlement list, an upgrade to the latest Run-time is required. Deprecated Feature List in getinfo Response The entitlement list is a super set that contains all details including the details contained in the feature list. For this reason, the feature list has become redundant and it will be deprecated in the future releases. For more details about the getinfo API's scope, format, and response, see Run-time Guide. getinfo Scope Enhancement In the getinfo API scope, it can be specified explicitly whether the getinfo call should be served from Cloud Connect or from local license store. The getinfo API scope contains an integer

11 Enhancements in This Release 11 parameter connectmode that controls whether to retrieve information locally or from Cloud. When not specified, getinfo follows the default behavior - same as was there in previous versions. In Java and.net, a new overload method Add has been provided that accepts connectmode. public void Add(String EID, String productname, SaaSFeatureNode featurenode, int connectmode) A new enumerator is used to provide values to the connectmode parameter. The enumerator is named as ConnectMode in Java and.net, and scr_connectmode_t in C. Its possible values are: o o CONNECTED(1): The getinfo call is served from Cloud Connect. If connection is not established, an error is returned. LOCAL(2): The getinfo call is served from local license store. The call is never sent to Cloud Connect. There is no change in the signature of the getinfo API. For details of getinfo scope and connectmode parameter, refer to Run-time Guide, section "Scope". Ability to Show or Hide Revoked Entitlements in EMS In EMS, the revoked entitlements were always considered during entitlement search, report generation, and in web services response. There was no provision to keep the revoked entitlements hidden and view them only when required. Now, EMS allows you to specify whether to hide or show the revoked entitlements. By default, revoked entitlements are not shown in EMS GUI entitlement search and in generated reports. Similarly, revoked entitlements are hidden in response of EMS web services. EMS GUI Entitlement Search The basic search and advanced search have been enhanced to filter entitlements by status. For details, see EMS User's Guide, section "Searching Entitlements". EMS Reports EMS reports contain a new input parameter Entitlement Status, which allows filtering of records based on status. Its valid values are Enabled, Disabled, Revoked, Enabled and Disabled, and All. The default selection is Enabled and Disabled. Following EMS reports have been modified: Customer Entitlement Report Custom Vendor Attribute Report Peak Provisioned Users Report User Usage Report Feature Usage Report Product Usage Report Remaining Executions Prepaid Report Feature Usage Based on Vendor Attribute Report Peak Capacity Report Vendor Info Usage Report Raw Usage Data Report For report details, see EMS User's Guide, section "Available Predefined Reports".

12 12 Sentinel Cloud V Release Notes EMS Web Services EMS web services have been modified to include a new parameter, status, in input and response. Its valid values are: 3 (include revoked entitlements) and 4 (do not include revoked entitlements). The following web services have been updated: getcustomerusagelog getcustomerusagelogbasedonvendorinfo getrawusagedataforcustomer retrievedetachdata retrievepeakcapacity searchentitlements For web service details, see EMS Web Services Guide. Controlling Detach of a Lower Duration License The ISV's customers were earlier allowed to detach licenses (by using the transfer call) for duration less than the duration of the currently active license. With this provision, there was possibility of license misuse by customer, as explained in the example below. Example Suppose a user detaches a license for 24 hours. The current station count is 1. After 2 hours, the same user requests second license for 12 hours. The license is granted. There is no change in station count since the license has been requested from same identity and same machine. After 12 hours, the second license expires freeing up the station count and thus enabling the user to detach another license. However, the first license (of 24 hours duration) is still running on the current machine. In this case, even though a license is active on the user s machine still an additional license becomes available on the server. This example shows the possible license misuse when license detach is allowed for duration less than the duration of the currently active license. Admin Console Setting It is ISV s decision whether or not to permit the case explained in the example above. The new Admin Console contains a configuration setting Lower detach duration support that can be used to allow or deny license detach for a lower duration. Note For the latest Run-time, this setting is disabled by default. We do not recommend enabling it as it may lead to license misuse. For existing ISVs who are using a previous version of Run-time (below 3.6) or Cloud Connect web services (below 1.2), this setting is enabled by default. This is to ensure that existing applications continue to behave as before. Changing the setting may result in an error ( by Run-time and 1044 by Cloud Connect web services). For the Feature Level on-premise licensing, this setting is applicable only for concurrent license model.

13 Enhancements in This Release 13 Maximum Detach Interval Increased The maximum value of detach interval has been raised to hours, for both on-premise entitlement level and on-premise feature level deployments. See EMS User's Guide, section "Admin Console" for details. Feature Selection During Detach (On-premise Feature Level Deployment Mode) A new sorting criterion has been added that helps in deciding which entitlement to serve when the same feature exists in multiple entitlements of a customer. If entitlement status is same and entitlement is of type on-premise feature level, then the feature whose license end date is nearest to the requested detach interval is considered for sorting. For details, see EMS User's Guide, section "Duplicate Feature in Multiple Entitlements of a Customer - Deciding Consumption Order". Support for Feature Name Authorization in Cloud Earlier for cloud applications, you could implement authorization based on only feature ID. Now, you can implement authorization based on either feature ID or feature name, similar to onpremise applications. Either feature ID or feature name should be used during the integration of your application with Run-time, and it should be done consistently. Using both interchangeably is not supported. Support for Feature Name Authorization in Cloud Connect Web Services Sentinel Cloud Connect web services also support authorization based on feature name. You can perform all authorization operations based on feature name similar to feature ID. EMS Web Services Enhancements Following are the enhancements in EMS web services: The searchcustomers web service has been enhanced to search customer records based on the ID of customer's contact (contact id). Following web services, which were earlier available to only ISVs, are now accessible to customer's contacts as well: searchcustomers and searchentitlements. The featurelist web service has been updated to introduce an additional element <enfid> in the response. It shows the feature ID that is used by protected applications for enforcement.

14 14 Sentinel Cloud V Release Notes Modified EMS Reports Following are the improvements in EMS reports: Report Peak Provisioned Users Report Vendor Info Usage Report Change Following are the changes: Provides a new input parameter to specify the entitlement status, such as Enabled, Disabled, Revoked, or All. The customer name parameter has been made optional. When it is left blank, the report retrieves data for all customers. The output also displays the type of peak provisioned user, such as retail, unnamed, or concurrent. This report can now be filtered based on the following parameters: Feature Name, Feature ID, and Vendor Data. By default, the records with blank and null vendor attribute values are not fetched from database. To fetch all records including blanks, the Vendor Data value should be specified as All. For report details, see EMS User's Guide, section "Available Predefined Reports". Enhanced Proxy Support With Automatic Proxy, the end user is not required to perform any proxy-specific changes in the Run-time configuration file, when the application runs in a no-proxy environment or in a WPAD proxy environment. It is recommended to set the default proxy mode to Automatic for onpremise applications. Automatic Proxy Authentication for Run-time on Linux For Linux environments, Run-time now supports automatic proxy authentication using system credentials (username and password). Allow Running Multiple Application Instances You can run multiple instances of an application from same or different locations, each of which can use same configuration file and usage file. Previously, it was required to customize configuration file and usage file path for every instance. Installer Changes The.NET utility for on-premise fingerprint management has been removed from the SDK installation directory. Quartz Jar Renamed The Quartz jar file used in Java Run-time has been renamed to SaaSQuartz.jar, so that customers can use any version of Quartz.

15 Enhancements in This Release 15 Important Notes Related to Cloud Connect Web Services Version When feature name authorization support was introduced, the version of Cloud Connect web services was changed from 1.0 to 1.1 (an intermediate version). The request message formats of login and getinfo calls from versions 1.1 onwards differ from that of 1.0, due to changes done to support feature name authorization. The latest version of Cloud Connect web services is 1.2. This version change was done to support on-premise named licenses. To maintain backward compatibility, the latest version 1.2 supports all the previous versions (1.0 and 1.1) in web service calls. See Cloud Connect Web Services Guide for details.

16 16 Sentinel Cloud V Release Notes Issues Fixed in This Release The following is a list of customer-reported issues that have been addressed in this release: Description If a license has been revoked and any of login, getinfo, or transfer APIs is called, the error returned is "10004: License is Revoked". The error returned earlier was "14000: License does not exist". The getinfo API will now return the error "14002: Invalid parameter (Customer)" if an invalid Customer ID is provided in the on-premise connected mode. Earlier, an application that terminated abnormally on Linux required you to manually clear the Run-time locks before you could re-launch the application. This issue has been fixed and the application's next execution does not require any manual intervention. EMS was not sending s on clicking the button that is available on viewing the entitlement certificate. This has been fixed. This functionality is independent of the Required value defined in Admin Console. It was ambiguous that product name and version were displayed together in various EMS screens, such as Product screen, Entitlements details screen, Add/Edit Product screen, reports, and so on. Now, the product name and version are displayed in different columns. The behavior of the Detach Interval field on the Add Product screen (available while creating an on-premise entitlement with the Entitlement Level feature caching mode) has been corrected so that it does not show the warning sign when the No Limit check box is first selected and then cleared. There was an issue with the Forgot Password functionality on EMS login screen (both vendor and customer login). On clicking the link, password was reset but the was not sent. Now, an is sent when the password is reset. But if the is not sent by EMS for any reason, the user is allowed to login by using the old password. Earlier, the Contact drop-down list on the New Entitlement screen of EMS displayed contacts even when the customer name was not specified. This has been corrected. Now a customer name must be selected to view the list of associated contacts in the Contact drop-down list. There were no proper validations on start date and end date while creating license model and reconfiguring entitlements on EMS GUI. For example, it was allowed to create a license model where start date is later than the end date. This has been rectified. The underscore character in customer name was allowed on the Create New Customer screen but was not allowed on the Edit Customer screen. The fix allows the underscore character on the Edit Customer screen as well. The Name field on the Add namespace screen was not highlighted when an incorrect input was provided. This has been fixed. Area Run-time Run-time Run-time EMS GUI EMS GUI EMS GUI EMS GUI EMS GUI EMS GUI EMS GUI EMS GUI

17 Issues Fixed in This Release 17 Description On the Edit User screen, the Password and Confirm Password fields were being displayed after clicking Submit. This has been fixed; these fields are displayed only when the edit icon (shown next to the Password field) is clicked. When an existing user ID was given while creating a retail entitlement, an error was not thrown immediately but at a later stage while committing the entitlement. Now, the error is thrown soon after the (already existing) user ID is entered. Similarly, the createentitlement.xml and updateentitlement.xml web services will return error if an already existing userid is specified during entitlement creation or update. When the retrieveactivestations web service is called and there are no active stations available, the response will show the OK status and a new element: <desc>no active stations found</desc>. When the addfeature.xml web service was called concurrently, there was a possibility of assigning the same featureid to multiple features by EMS. Now, proper checks have been implemented to ensure that a unique featureid is generated for each feature The retrievepeakcapacity EMS web service will now return the error 1180, instead of 309, if no usage is found for the specified parameter values. The loginbycontact EMS web service now also returns entid in response. If there are more than one active stations for an entitlement, the retrieveactionstations EMS web service returns multiple records in the response XML, all containing same values for the fingerprintid and friendlyname fields. This has been fixed and the correct values are returned. The retreiveentilementfingerprint web service in EMS used to return only 10 fingerprints. Now it retrieves all the fingerprints registered for an entitlement. The deleteentitlementfingerprint EMS web service was working well with vendor login, but threw an error with contact login : Fingerprint Id does not exist. Provide a valid Fingerprint Id. This has been fixed. The deleteentitlementfingerprint and deletefingerprint web services used to delete a fingerprint based on 'fingerprint ID', which was a simple integer and error prone. To secure the deletion process, additional validations have been added. Now, deleteentitlementfingerprint.xml also requires 'eid' and deletefingerprint.xml requires 'customerrefid' before the deletion. The maximum value of Station Count (for the on-premise Entitlement Level feature caching mode) was fixed to 50. It has been made configurable now and can be changed by SafeNet as per ISV's request. There were no proper validations on start date and end date while creating license model and reconfiguring entitlements on EMS GUI. For example, it was allowed to create a license model where start date is later than the end date. This has been rectified. Area EMS GUI EMS GUI and EMS web service EMS web service EMS web service EMS web service EMS web service EMS web service EMS web service EMS web service EMS web service EMS GUI, EMS web Service, Runtime EMS GUI

18 18 Sentinel Cloud V Release Notes Description When the concurrency limit is reached for first entitlement/product, the license is served from the second entitlement/product if concurrency is available. This is called concurrency switching. Note: Concurrency switching is backward compatible. With Cloud Connect version 3.6, all previous versions of Run-time and Cloud Connect web services (below 3.6) will also support concurrency switching. In the Run-time Guide, the parameter table of each API has been modified to explicitly mention if a parameter is mandatory or optional. The input parameter for retrievefingerprint web service in EMS Web Services Guide has been corrected from "CustInfo" to "customerinfo". The sample code of the verifylogin web service has been corrected in EMS Web services guide. Area Sentinel Cloud Connect Documentation Documentation Documentation

19 Platforms Tested 19 Platforms Tested Sentinel Cloud Run-time has been tested on the following platforms: Run-time Run-time Interface Platforms Tested Cloud Java Windows.NET C Linux Windows 2012 Windows 8 Windows 8.1 Windows 7 Windows Server 2008 Ubuntu 14 CentOS 5.4 Red Hat Enterprise Linux (RHEL) 6.3 SUSE 12.1 Windows Windows 2012 Windows 8 Windows 8.1 Windows 7 Windows Server 2008 Windows Windows 2012 (64-bit) Windows 8.1 (64-bit) Windows 8 (64-bit) Windows 7 (32-bit and 64-bit) Windows Server 2008 (32-bit and 64-bit) Linux (32-bit and 64-bit) Ubuntu 14 CentOS 5.4 Red Hat Enterprise Linux (RHEL) 6.3 SUSE 12.1 Run-time Environment Web Server JRE 7.0 Tomcat 7.NET Framework 2.0 and IIS 6.0 and 7.0

20 20 Sentinel Cloud V Release Notes Run-time Run-time Interface Platforms Tested Run-time Environment Web Server Onpremise Java Windows Windows 2012 (64-bit) JRE 7 Tomcat 7 Windows 8.1 (64-bit) Windows 8 (64-bit) Windows 7 (32-bit and 64-bit) Windows Server 2008 (32-bit and 64-bit) Linux Ubuntu 14 CentOS 5.4 Red Hat Enterprise Linux (RHEL) 6.3 SUSE 12.1.NET Windows Windows 2012 Windows 8.NET Framework 2.0 and 3.5 IIS 6.0 and 7.0 Windows 8.1 Windows 7 Windows Server 2008 C Windows - - Windows 2012 (64-bit) Windows 8.1 (64-bit) Windows 8 (64-bit) Windows 7 (32-bit and 64-bit) Windows Server 2008 (32-bit and 64-bit) Linux (32-bit and 64-bit) Ubuntu 14 CentOS 5.4 Red Hat Enterprise Linux (RHEL) 6.3 SUSE 12.1

21 Web Browsers Supported 21 Web Browsers Supported Sentinel Cloud EMS GUI is best viewed with the following Web browsers: Browser Version Internet Explorer 11.x Mozilla FireFox 37.x Google Chrome 42.0

22 22 Sentinel Cloud V Release Notes Known Issues The known issues in Sentinel Cloud v.3.6 that are likely to have the most significant impact on users are listed below. Billing Related The billing data provided in the customer login is the partially processed data. It is used to produce the final bill, and should not be considered as the final bill. Any exception encountered while retrieving billing details is logged in Billing.xml file, but not displayed on Sentinel Cloud EMS GUI. Sentinel Cloud EMS Related On EMS Home Page, the color coding of legends shown for The Top 5 Customers pie chart appear ambiguous. The Customers and Entitlements pages display a list of associated contacts under the Contact Association group. When you click a contact and click the Delete button in the popup that appears, the contact is not deleted. The License Subscription Expired rule does not trigger notification if a license is not activated in its lifecycle and it expires. If products are added to a reconfigured entitlement, the information related to added products is not available in generated reports. For User ID, the following special characters are blocked from EMS but are allowed from Runtime: <,>,",^,&,%. As a result, the User IDs containing these characters are not displayed on EMS screens. The notification is not sent if feature name or product name contains the $ character. On the Notification Rule page, you can use the Reset button to clear parameter values only if you have not clicked the Submit button even once. Installer Related When you upgrade to a higher version of Sentinel Cloud Services, the installer uninstalls the SDK from the custom location and performs the installation at the default location. We recommend uninstalling the earlier versions before installing a higher version of Sentinel Cloud Services, and manually removing the files that are not removed during uninstallation. Terminal Server Support Related Terminal server support is not available for applications hosted on IIS server. Run-time APIs Related For on-premise Entitlement Level feature caching mode, the getinfo API returns 0 instead of returning the actual number of active logged-in sessions for concurrent features. This issue exists on WIndows and Linux both.

23