Hi Krystian,

So in Guilin CLAMP we login to the UI without using SSL client authentication (org.onap.clamp.p12 imported to the browser)?
        à In guilin, you can use both (certificate or basic auth, normally the user “demo”, pass “demo123456!” is provisioned with the right AAF permissions by default), Frankfurt you must use an AAF certificate

Instead, we start using the user login/password by default?

• As said you can since Guilin use the default user “demo”or create one in AAF with clamp permission, and you can use X509 or basic auth login.

Or how to get the client certificate to deploy by OOM (to use during CLAMP UI login process)?

• You can get the certificate on the clamp wiki but I believe this one has expired, so it must be renewed.

In Guilin you can renew the Clamp user certificate in AAF and get it for the login or you can get the p12 from OOM installation in the clamp-backend docker (do a find / -name “*.p12”)

                Normally /opt/app/osaaf/local

Seb