Cisco Cisco Prime Service Catalog 11.0

ページ / 10
5
Release Notes for Cisco Prime Service Catalog 11.0
  New Features and Enhancements in Prime Service Catalog 11.0
Security Enhancements
Prime Service Catalog now uses TLS v1.2 protocol for the connection with:
LDAP
AMQP message broker
Virtual appliance via httpd
SSH connections to the virtual appliance use strong ciphers.
API Enhancements
nsAPI Enhancements
Managing Service Definitions through Sync APIs
nsAPIs have now been enhanced to allow dynamic sync of associations to categories, facets, 
extensions for a service or to entirely delete the service
Connecting to UCSD/ICFB/Puppet 
Connection APIs [such as AMQP Environment, cloud-connection type (UCSD/ICFB/PUPPET)] has 
been developed to fetch credentials, host, port, and SSL certificates from Orchestration service and 
establish a connection for this service.
Encrypting Credentials using Public Key GUID
Prime Service Catalog supports a secure way to return AMQP credentials, using the GUID of the 
Public Key passed to the nsAPI.
Other Enhancements
The Message Broker Overview API has been enhanced (with the use of noCache parameter) to 
ensure the latest information is fetched when you directly access database connected to 
RabbitMQ server.
New nsAPI to update or modify the Service Form data.
These API enhancements are covered in the 
Features Introduced in 10.1 Patch Releases 
New features added in cumulative patch releases of Cisco Prime Service Catalog 10.1, for example, 
service form improvements, catalog deployer’s performance improvement by reducing the package 
deployment time, and so on. For more details about these patch release features, see the patch readmes
These features are also rolled up to Cisco Prime Service Catalog 11.0.