Hi Rahul,I am glad it helped.You have correctly identified where to
replace the AAI part of the AAF-certificates (you also have to do it in this
project oom/kubernetes/aai/charts/aai-resources), but you also need to replace
the certificate in the AAF project - I never did this, so I am unable to help
you further. I heard there is a tool for generating the certificates and the
appropriate property files (I don’t know any specifics), you probably should
use that.You can reach out to Jonathan Gathman, it won’t be a problem for him
to tell you how to do it as he is the author of AAF and he created all the
certificates for ONAP projects :)Br,Pavel---- On Sun, 18 Nov 2018 18:28:31
+0100 Rahul Sharma<[email protected]> wrote ----Thank you Pavel. The
insights about interaction between AAI and AAF was helpful. I disabled AAF as
you recommended and we are now able to communicate with AAI :-) !!We have
already tried with the default values and they work. However in our dev
environment, each dev is allocated a separate namespace, persistent mountpath
and nodeport-prefix and we need to stick to them. What we really want is
working ONAP with AAF enabled. AAF is actually up and running in my dev
environment but AAI isn't able to communicate with it.Do you know if we can
generate AAF cert using a specific namespace (rather than onap) and put it
under the
oom/kubernetes/aai/charts/aai-traversal/resources/config/aaf/org.onap.aai.keyfile.
I suppose that's the cert you are talking about?That would be really help
unblock us.Regards,Rahul
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13828): https://lists.onap.org/g/onap-discuss/message/13828
Mute This Topic: https://lists.onap.org/mt/28195431/21656
Mute #aai: https://lists.onap.org/mk?hashtag=aai&subid=2740164
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
