Open Stack

Public bug reported:

An IBM user wanted to communicate with our backend CoprHD driver using certificate. But right now, there is not provision to do so. CoprHD should provide an option in config to perform all operations (REST API calls)
using certificate verification. Both CA signed and self-signed certificates should be supported.

** Affects: cinder
     Importance: Undecided
     Assignee: Vinita Deshpande (vinita)
         Status: In Progress


** Tags: coprhd security

** Changed in: cinder
       Status: New => In Progress

** Changed in: cinder
     Assignee: (unassigned) => Vinita Deshpande (vinita)

** Description changed:

- An IBM user wanted to communicate with our backend CoprHD driver using SSL. But right now, there is not provision to do so. CoprHD should provide an option in config to perform all operations (REST API calls)
+ An IBM user wanted to communicate with our backend CoprHD driver using certificate. But right now, there is not provision to do so. CoprHD should provide an option in config to perform all operations (REST API calls)
  using certificate verification. Both CA signed and self-signed certificates should be supported.

-- 
You received this bug notification because you are a member of OpenStack
Security, which is subscribed to OpenStack.
https://bugs.launchpad.net/bugs/1653626

Title:
  IBM User tries to communicate with CoprHD securely, but fails to do so

Status in Cinder:
  In Progress

Bug description:
  An IBM user wanted to communicate with our backend CoprHD driver using certificate. But right now, there is not provision to do so. CoprHD should provide an option in config to perform all operations (REST API calls)
  using certificate verification. Both CA signed and self-signed certificates should be supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1653626/+subscriptions