Embed Size (px)
Citation preview
Sentinel Cloud V.3.6Release Notes
2 Sentinel Cloud V.3.6 - Release Notes
Document Revision History
Part number 007-012135-001, Revision K
May 2015
Disclaimer and Copyrights
Copyright © 2015, SafeNet, Inc. All rights reserved. http://www.safenet-inc.com/
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.
ContentsAbout This Document 4Product Overview 4Documentation Resources 4Obtaining Support 4What's New in This Release? 5
New EMS Admin Console 5Named Entitlement Support (On-premise Entitlement Level) 5Usage Data Management in Isolated Networks (On-premise) 6Control License Use on Virtual Machines and Support Clone Protection 7GUID Support in Customer Reference ID 7Support for Sales Representative E-mail Address in EMS Web Services 8New EMS Web Services 8New EMS Reports 9
Enhancements in This Release 10getInfo Scope and Format Aligned Across Cloud and On-premise Deployments 10getInfo Scope Enhancement 10Ability to Show or Hide Revoked Entitlements in EMS 11Controlling Detach of a Lower Duration License 12Maximum Detach Interval Increased 13Feature Selection During Detach (On-premise Feature Level Deployment Mode) 13Support for Feature Name Authorization in Cloud 13Support for Feature Name Authorization in Cloud Connect Web Services 13EMS Web Services Enhancements 13Modified EMS Reports 14Enhanced Proxy Support 14Automatic Proxy Authentication for Run-time on Linux 14Allow Running Multiple Application Instances 14Installer Changes 14Quartz Jar Renamed 14Important Notes Related to Cloud Connect Web Services Version 15
Issues Fixed in This Release 16Platforms Tested 19Web Browsers Supported 21Known Issues 22
4 Sentinel Cloud V.3.6 - Release Notes
Sentinel Cloud V.3.6 - Release Notes
About This DocumentThis 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:
http://documentation.sentinelcloud.com/RN/ReleaseNotes.pdf
Product OverviewSentinel® 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 http://documentation.sentinelcloud.com/CRTG/.
Documentation ResourcesVisit documentation.sentinelcloud.com to access the complete product documentation.
Obtaining SupportYou can contact us by using any of the following options:
n Business Contacts - To find the nearest office or distributor, use the following URL: http://www.safenet-inc.com/contact-us/
n Technical Support - To obtain assistance in using SafeNet products, feel free to contact our Technical Support team:
o Phone: 800-545-6608 (US toll free), +1-410-931-7520 (International)
o E-mail: [email protected]
o URL: http://sentinelcustomer.safenet-inc.com/sentinelsupport/
n Downloads - You can download installers and other updated components using this URL:www.sentinelcustomer.safenet-inc.com/sentineldownloads/
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 :
n Configure on-premise licensing settings, such as detach interval, cache interval, virtual machine support, and clone protection.
n Specify range and default values of Time to Live (TTL) properties for postpaid and sub-scription license models.
n Control settings that determine how abandoned sessions are handled and concurrency is managed, such as session timeout and minimum usage count.
n Configure outgoing e-mail exchange server settings, such as SMTP host and port.
n Control the availability of entitlement certificate e-mails, specify the intended recipients, and customize e-mail subject lines.
n Specify the technical support information to be mentioned in EMS e-mails, 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 on-premise 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.
What's New in This Release? 5
6 Sentinel Cloud V.3.6 - Release Notes
Compatibility Information:
n 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).
n The old Run-times cannot consume named entitlements; they throw the -20002 internal error.
n Since change from named to unnamed (or vice versa) is not allowed during recon-figuration, the old entitlements (created with EMS versions older than 3.6) will remain unnamed.
n 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:
n A master file with the name clientDetails.
n A usage file with the extension *.$$$.
2. From the connected machine, the transfer API is called with the following:
n The SYNC_USAGE_CUSTOM(32) action.
n 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.
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:
n VM Enabled: Used to specify whether or not a protected application should run in vir-tualized environment.
n 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
n The ability to control license use on virtual and cloned environments is available for on-premise Entitlement Level feature caching mode only.
n For on-premise Feature Level feature caching mode, both VM Enabled and Clone Pro-tection 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.
What's New in This Release? 7
8 Sentinel Cloud V.3.6 - Release Notes
Support for Sales Representative E-mail Address in EMS Web Services
EMS web services now allow you to specify e-mail address of a person representing the software vendor, such as a sales representative, while creating or updating an entitlement. A new optional parameter alternateEmailId has been introduced in createEntitlement and updateEntitlement web services to support this.
Note:
n A sales representative's email address can be associated to entitlements belonging to dif-ferent customers.
n The entitlement certificate e-mails are also sent to sales representative, if:
o E-mails are enabled, that is, the E-mail Required field is set to Desired in EMS Admin Console.
o The value of E-mail Recipients is set to ISV or Both in EMS Admin Console.
n If notification rules are enabled, the e-mail 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 Description
Related Sec-tion in EMS Web Services Guide
retrieveDetachData 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 on-premise entitlements.
The data is reported for those sessions that have been detached after upgrading to Sentinel Cloud 3.6 back end.
Retrieve Detached Session Data
getRawUsageDataForCustomer 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.
Retrieve Customer Raw Usage Data
Web Service Description
Related Sec-tion in EMS Web Services Guide
retrieveFingerprintRegistrationDetails Retrieves friendly name of a machine and EID registered to a fingerprint.
Retrieve Fingerprint Registration Details
searchContacts Searches contacts for the given query parameters.
Search Contacts
New EMS Reports
Following EMS reports have been introduced in this release:
Report Change
Raw Usage Data Report
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.
Peak Capacity Report
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".
What's New in This Release? 9
10 Sentinel Cloud V.3.6 - 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:
n The getInfo API can provide hierarchical view of details available at various levels - enti-tlement, product, feature, and license attributes – for on-premise deployments.
n 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.
Note
n Following additional details are retrieved at feature level for on-premise deployments:
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 fea-ture caching modes.
o 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.
n Following details are not retrieved at feature level for on-premise deployments:
o Start date
o Notification information
Upgrade Note
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
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.
n 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 con-
nectMode)
n A new enumerator is used to provide values to the connectMode parameter. The enu-merator is named as ConnectMode in Java and .NET, and scr_ConnectMode_t in C. Its possible values are:
o CONNECTED(1): The getInfo call is served from Cloud Connect. If connection is not established, an error is returned.
o LOCAL(2): The getInfo call is served from local license store. The call is never sent to Cloud Connect.
n 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:
n Customer Entitlement Report n Custom Vendor Attribute Report n Peak Provisioned Users Report n User Usage Report n Feature Usage Report n Product Usage Report
n Remaining Executions Prepaid Report n Feature Usage Based on Vendor Attribute
Report n Peak Capacity Report n Vendor Info Usage Report n Raw Usage Data Report
For report details, see EMS User's Guide, section "Available Predefined Reports".
Enhancements in This Release 11
12 Sentinel Cloud V.3.6 - 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:
n getCustomerUsageLog n getCustomerUsageLogBasedOnVendorInfo n getRawUsageDataForCustomer
n retrieveDetachData n retrievePeakCapacity n 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
n For the latest Run-time, this setting is disabled by default. We do not recommend enabling it as it may lead to license misuse.
n For existing ISVs who are using a previous version of Run-time (below 3.6) or Cloud Con-nect web services (below 1.2), this setting is enabled by default. This is to ensure that exist-ing applications continue to behave as before. Changing the setting may result in an error (-20000 by Run-time and 1044 by Cloud Connect web services).
n For the Feature Level on-premise licensing, this setting is applicable only for concurrent license model.
Maximum Detach Interval Increased
The maximum value of detach interval has been raised to 175200 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 on-premise 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 sup-ported.
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:
n The searchCustomers web service has been enhanced to search customer records based on the e-mail ID of customer's contact (contactEmailId).
n Following web services, which were earlier available to only ISVs, are now accessible to cus-tomer's contacts as well: searchCustomers and searchEntitlements.
n 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 enforce-ment.
Enhancements in This Release 13
14 Sentinel Cloud V.3.6 - Release Notes
Modified EMS Reports
Following are the improvements in EMS reports:
Report Change
Peak Provisioned Users Report
Following are the changes: n Provides a new input parameter to specify the entitlement status, such as
Enabled, Disabled, Revoked, or All. n The customer name parameter has been made optional. When it is left
blank, the report retrieves data for all customers. n The output also displays the type of peak provisioned user, such as retail,
unnamed, or concurrent.
Vendor Info Usage Report
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 on-premise 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.
Important Notes Related to Cloud Connect Web Services Version
n 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).
n 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.
n The latest version of Cloud Connect web services is 1.2. This version change was done to support on-premise named licenses.
n To maintain backward compatibility, the latest version 1.2 supports all the previous ver-sions (1.0 and 1.1) in web service calls.
See Cloud Connect Web Services Guide for details.
Enhancements in This Release 15
16 Sentinel Cloud V.3.6 - Release Notes
Issues Fixed in This ReleaseThe following is a list of customer-reported issues that have been addressed in this release:
Description Area
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".
Run-time
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.
Run-time
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.
Run-time
EMS was not sending e-mails on clicking the E-mail button that is available on viewing the entitlement certificate. This has been fixed. This functionality is independent of the E-mail Required value defined in Admin Console.
EMS GUI
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.
EMS GUI
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.
EMS GUI
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 e-mail was not sent. Now, an e-mail is sent when the password is reset. But if the e-mail is not sent by EMS for any reason, the user is allowed to login by using the old password.
EMS GUI
Earlier, the Contact E-mail 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 E-mail drop-down list.
EMS GUI
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.
EMS GUI
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.
EMS GUI
The Name field on the Add namespace screen was not highlighted when an incorrect input was provided. This has been fixed.
EMS GUI
Description Area
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.
EMS GUI
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.
EMS GUI and EMS web service
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>.
EMS web service
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
EMS web service
The retrievePeakCapacity EMS web service will now return the error 1180, instead of 309, if no usage is found for the specified parameter values.
EMS web service
The loginByContact EMS web service now also returns entId in response. EMS web service
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.
EMS web service
The retreiveEntilementFingerprint web service in EMS used to return only 10 fingerprints. Now it retrieves all the fingerprints registered for an entitlement.
EMS web service
The deleteEntitlementFingerprint EMS web service was working well with vendor login, but threw an error with contact login - 1106: Fingerprint Id does not exist. Provide a valid Fingerprint Id. This has been fixed.
EMS web service
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.
EMS web service
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.
EMS GUI, EMS web Service, Run-time
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.
EMS GUI
Issues Fixed in This Release 17
18 Sentinel Cloud V.3.6 - Release Notes
Description Area
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.
Sentinel Cloud Connect
In the Run-time Guide, the parameter table of each API has been modified to explicitly mention if a parameter is mandatory or optional.
Documentation
The input parameter for retrieveFingerprint web service in EMS Web Services Guide has been corrected from "CustInfo" to "customerInfo".
Documentation
The sample code of the verifyLogin web service has been corrected in EMS Web services guide.
Documentation
Platforms TestedSentinel Cloud Run-time has been tested on the following platforms:
Run-time Run-time Interface
Platforms Tested Run-time Environment
Web Server
Cloud Java Windows n Windows 2012 n Windows 8 n Windows 8.1 n Windows 7 n Windows Server 2008
Linux n Ubuntu 14 n CentOS 5.4 n Red Hat Enterprise Linux
(RHEL) 6.3 n SUSE 12.1
JRE 7.0 Tomcat 7
.NET Windows n Windows 2012 n Windows 8 n Windows 8.1 n Windows 7 n Windows Server 2008
.NET Framework 2.0 and 3.5
IIS 6.0 and 7.0
C Windows n Windows 2012 (64-bit) n Windows 8.1 (64-bit) n Windows 8 (64-bit) n Windows 7 (32-bit and 64-bit) n Windows Server 2008 (32-bit
and 64-bit)Linux (32-bit and 64-bit)
n Ubuntu 14 n CentOS 5.4 n Red Hat Enterprise Linux
(RHEL) 6.3 n SUSE 12.1
- -
Platforms Tested 19
20 Sentinel Cloud V.3.6 - Release Notes
Run-time Run-time Interface
Platforms Tested Run-time Environment
Web Server
On-premise
Java Windows n Windows 2012 (64-bit) n Windows 8.1 (64-bit) n Windows 8 (64-bit) n Windows 7 (32-bit and 64-bit) n Windows Server 2008 (32-bit
and 64-bit)Linux
n Ubuntu 14 n CentOS 5.4 n Red Hat Enterprise Linux
(RHEL) 6.3 n SUSE 12.1
JRE 7 Tomcat 7
.NET Windows n Windows 2012 n Windows 8 n Windows 8.1 n Windows 7 n Windows Server 2008
.NET Framework 2.0 and 3.5
IIS 6.0 and 7.0
C Windows n Windows 2012 (64-bit) n Windows 8.1 (64-bit) n Windows 8 (64-bit) n Windows 7 (32-bit and 64-bit) n Windows Server 2008 (32-bit
and 64-bit)Linux (32-bit and 64-bit)
n Ubuntu 14 n CentOS 5.4 n Red Hat Enterprise Linux
(RHEL) 6.3 n SUSE 12.1
- -
Web Browsers SupportedSentinel 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
Web Browsers Supported 21
22 Sentinel Cloud V.3.6 - Release Notes
Known IssuesThe 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 pop-up 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 Run-time: <,>,",^,&,% . As a result, the User IDs containing these characters are not displayed on EMS screens.
The notification e-mail 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.
