It is good to highlight both your server and client interfaces.

Brian



Sent via the Samsung Galaxy S8, an AT&T 4G LTE smartphone


-------- Original message --------
From: "NGUEKO, GERVAIS-MARTIAL" <[email protected]>
Date: 10/19/18 12:40 PM (GMT-05:00)
To: [email protected], "DRAGOSH, PAM" <[email protected]>, 
"HERNANDEZ-HERRERO, JORGE" <[email protected]>, "ZWARICO, AMY" <[email protected]>
Subject: Re: [onap-discuss] ONAP Support for Secure Communication

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

Hi Amy,

Here below more details on the secure communication on CLAMP, the reason behind 
my original “No” answer:
CLAMP UI itself is https and communication between frontend and backend is 
secured. but

  *   SDC communication is http and so not secure (sdc doesn’t support AAF and 
has not exposed a secure API till now), similar to Policy we use the sdc client 
so it will be up to SDC team to provide us a secured client.
  *   Call from CLAMP to DCAE inventory API is http so not secure(DCAE is not 
integrated with AAF and has not exposed this API in https). Other DCAE API, 
used by CLAMP for deployment triggering, are https and so are secured.
  *   Policy calls are secured.

Br,
Martial

From: [email protected] <[email protected]> On Behalf Of 
DRAGOSH, PAM
Sent: vendredi 19 octobre 2018 17:43
To: [email protected]; DRAGOSH, PAM <[email protected]>; 
HERNANDEZ-HERRERO, JORGE <[email protected]>
Subject: Re: [onap-discuss] ONAP Support for Secure Communication

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Correction – the policy distribution application has 2 endpoints. One for 
HealthCheck that will need https, and the other I mentioned is the SDC Client 
SDK that will need to support https.

Sorry

Pam

From: <[email protected]<mailto:[email protected]>> on 
behalf of "DRAGOSH, PAMELA L (PAM)" 
<[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>, "DRAGOSH, 
PAMELA L (PAM)" <[email protected]<mailto:[email protected]>>
Date: Friday, October 19, 2018 at 2:00 AM
To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>, 
"HERNANDEZ-HERRERO, JORGE" <[email protected]<mailto:[email protected]>>
Subject: Re: [onap-discuss] ONAP Support for Secure Communication

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Amy – the policy distribution application uses the SDC Client SDK for http 
communication via dmaap. It will be up to that project to support https, not 
policy project.

Our other component is not MVP to this release and will have https for Dublin.

Pam

From: <[email protected]<mailto:[email protected]>> on 
behalf of "HERNANDEZ-HERRERO, JORGE" <[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>, 
"HERNANDEZ-HERRERO, JORGE" <[email protected]<mailto:[email protected]>>
Date: Thursday, October 18, 2018 at 8:05 PM
To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Subject: Re: [onap-discuss] ONAP Support for Secure Communication

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.


Yes, correct, that’s the plan.  -Jorge

From: ZWARICO, AMY
Sent: Thursday, October 18, 2018 8:49 PM
To: [email protected]<mailto:[email protected]>; 
HERNANDEZ-HERRERO, JORGE <[email protected]<mailto:[email protected]>>
Subject: RE: [onap-discuss] ONAP Support for Secure Communication

Thank you. Are there plans to support https for the new components in Dublin?

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of HERNANDEZ-HERRERO, JORGE
Sent: Thursday, October 18, 2018 7:13 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [onap-discuss] ONAP Support for Secure Communication

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

Hello Amy,



Responding on behalf of Pam D., Policy PTL, that is currently on vacations.



https is supported across all policy components with the exception of the new 
ones introduced in Casablanca release (apex-pdp, policy-distribution).



Jorge


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13149): https://lists.onap.org/g/onap-discuss/message/13149
Mute This Topic: https://lists.onap.org/mt/27369768/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to