Hi, I am working on a project that was created recently using the AEM
6.5 archetype base project for best practices LINK and we have run into
a few scenarios where we have added a dependency, then we
code/build/deploy and the bundle will not start because it cannot import
a needed package. I guess it is expecting to find the package exported
from some other OSGi bundle.We solve this by adding the needed packages
to the bnd-maven-plugin config under "-conditionalpackage"
Yes, open that site in a browser, view certificate, view certification
path, and there you should find the CAs that must be trusted. In my
case, I had 3 corporate CAs related to proxy that I had to add to java
keystore. It is very important that you do this for the SAME java
install that your local AEM is using to run. I had the same exact error
and this solved it for me, as well as for another person in my
organization. I wish you luck.
I actually solved this issue by adding the relevant CA certificates into
the Java keystore used by the java installation that runs my local AEM.
Once that was done, the health check test call to get a token began to
work. The reason I had this issue is because my corporate proxy does SSL
interception. My java install did not trust the corporate proxy.
I have this error too. Do you have a corporate proxy doing SSL
interception? My theory is that may be my problem. I have tried adding
the necessary CA certificates to the "global trust store" and it does
nothing to help. Anyone from Adobe want to respond ??