Invalid handling of external system certificates

Description

In AAI the certificate is described as

ssl-cacert: string

ca file content if enabled ssl on auth-url.

in ESR GUI it is an URL  see attachment

in VF-C API it is an URL see swagger definition

"certificateUrl": { "type": "string", "description": "vnfm certificate Url" },

It would be great to come to a conclusion where this bug belongs: AAI / MSB / VF-C / ESR?

Is it an URL or a content?

 

Environment

None

Attachments

1
  • 27 Apr 2018, 02:40 PM

Confluence content

mentioned on

Activity

Show:

Former user March 28, 2019 at 12:28 PM

Closing this because I think it was a typo on the attribute name that was fixed, please re-open if still an issue.

Former user March 20, 2019 at 8:51 PM

this was fixed with that patch on the typo on the attribute name, correct?

Former user November 22, 2018 at 9:26 AM

I tried with ssl cacert of ESR GUI and found the input to ssl cacert does not actually stored into AAI. If you refresh the ESR portal after your test, the input to ssl cacert will disappear , so it seems the input to ssl cacert is just in cache?

Former user November 20, 2018 at 8:23 AM

I would wonder if anyone has tested it? If I recall correctly, I had tried to input the cert but failed, either because the input box is not allowed to input long string (multiple line?), or ESR GUI does not actually get the input from GUI and store into AAI. But anyway, the certificates cannot be on-boarded. Thanks

Former user November 20, 2018 at 7:14 AM

I checked the code, the certifications already stored to aai while vim registration. The name is "ssl Cacert" in the ers gui.

 

 the auth param is "certificateUrl"  as below while registrate vnfm. do you think it is necessary to change this param to "Collection of PEM encoded trusted certificates" as said before or you should just keep this as right now?
"certificateUrl": { "type": "string", "description": "vnfm certificate Url" },

Done

Details

Assignee

Reporter

Fix versions

Affects versions

Priority

Created April 27, 2018 at 2:43 PM
Updated September 5, 2019 at 12:05 PM
Resolved March 28, 2019 at 12:28 PM

Flag notifications