-
Bug
-
Resolution: Done
-
Medium
-
El Alto Release
-
None
When using aai-data as a data source (the REST resource resolution mechanism), there is a problem with AAI certificates not being recognized as trusted. My AAI parameter definition looks like the following:
"my-aai-parameter" : { "tags" : "my-aai-parameter", "name" : "my-aai-parameter", "property" : { "description" : "my-aai-parameter", "type" : "string" }, "updated-by" : "someone", "sources" : { "input" : { "type" : "source-input" }, "default" : { "type" : "source-default", "properties" : { } }, "aai-data" : { "type" : "source-rest", "properties" : { "verb" : "GET", "type" : "JSON", "url-path" : "/aai/v14/network/generic-vnfs/generic-vnf/$vnf-id", "path" : "/my-aai-parameter", "input-key-mapping" : { "vnf-id" : "vnf-id" }, "output-key-mapping" : { "my-aai-parameter" : "my-aai-parameter" }, "key-dependencies" : [ "vnf-id" ] } } } }
I noticed that there has been once a discussion on this topic:
https://lists.onap.org/g/onap-discuss/topic/cds_aai/34441318?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,34441318
For debugging purposes, I temporarily disabled TLS certificate verification in CDS to see what will happen. It appears that aai-data has a problem with headers not being set while calling AAI REST API. The headers that are required but missing:
X-FromAppId X-TransactionId
Log file from cds-controller-blueprint pod is attached.