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

Bug #1653626 reported by Vinita Deshpande on 2017-01-03
This bug affects 2 people
Affects Status Importance Assigned to Milestone

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.

Changed in cinder:
status: New → In Progress
assignee: nobody → Vinita Deshpande (vinita)
description: updated

Unassigning due to no activity for > 6 months.

Changed in cinder:
assignee: Vinita Deshpande (vinita) → nobody

Change abandoned by Eric Harney (<email address hidden>) on branch: master
Reason: In merge conflict since July

Eric Harney (eharney) on 2019-02-05
Changed in cinder:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers