error in fulfillment setup (ACS4 on Debian)

[David_Adone]

Im trying to install Adobe Content Server 4 on a Linux server. But I’ve got a problem with the fulfillment component.

Using the Quickstart guide, everything was OK: generate the p12 file, install the admin package, those steps are done and validated, since I’m able to log in to the admin console and that I’ve changed the admin password from park345 to a new one.

But right now, the page http://server:port/fulfillment/statuscheck displays a HTTP 500 error.

So, I restart Tomcat 6, and look at the page http://server:port/fulfillment/Status?verbose=true:

exception :

javax.servlet.ServletException: L'exécution de la servlet a lancé une exception

cause mère :

java.lang.Error: Cound not find server's certificate in the keystore

       com.adobe.adept.fulfillment.security.ServerConfig.init(ServerConfig.java:161)

       com.adobe.adept.fulfillment.security.ServerConfig.getSigningURL(ServerConfig.java:48)

       com.adobe.adept.fulfillment.servlet.FulfillmentServerStatus.getServers(FulfillmentServerStatus.java:34)

       com.adobe.adept.common.servlet.Status.checkUp(Status.java:355)

       com.adobe.adept.common.servlet.Status.doGet(Status.java:421)

       javax.servlet.http.HttpServlet.service(HttpServlet.java:617)

       javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

If I try to reload the page, the message changes:

exception :

java.lang.NullPointerException

       com.adobe.adept.fulfillment.servlet.FulfillmentServerStatus.getServers(FulfillmentServerStatus.java:35)

       com.adobe.adept.common.servlet.Status.checkUp(Status.java:355)

       com.adobe.adept.common.servlet.Status.doGet(Status.java:421)

       javax.servlet.http.HttpServlet.service(HttpServlet.java:617)

       javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

What's wrong in my setup ?

[Guest]

The key part of the error is this:  "Cound not find server's certificate in the keystore"

This means that the fulfillment service is having problems processing the .p12 file specified in your fulfillment configuration file.

The common set of errors here are:

- You didn't create a .p12 file

- You didn't create the .p12 file correctly

- You didn't specify the correct file URL in the config file

- You didn't specify the correct password

(basically review the "Operator Enrollment" steps in the Quick Start guide and make sure you have done the correctly).

The biggest undocumented gotcha is that, if when creating the .p12 file you specified a name other than "operator", this won't work (it's a known bug that will get fixed, most likely in the next major dot release).

[David_Adone]

Hi Jim,

Thanks for the tips. Actually the .p12 is OK (or at least, seems to be OK when I check it). The password is correct, and the URL is also the good one.

But you maybe found what's the problem: I specified another name when I created my .p12 file. So, I will try to change this value (with a new .p12 file, and the according modification in the fulfillment.conf file) and I'll tell you if it's better after.