Error when fetching datahub for version using curl

[d_j_boyd]

SAP Commerce V 1811 MAC

Following steps under https://help.hybris.com/1811/hcd/6f2640dad2194c908fc7a8f9906a081a.html

Now when I execute curl -G https://localhost:9012/datahub-webapp/v1/version, I get

curl: (60) SSL certificate problem: self signed certificate More details here: https://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. HTTPS-proxy has similar options --proxy-cacert and --proxy-insecure.

I tried curl -k https://localhost:9012/datahub-webapp/v1/version, but in this case I get a HTTP Status 401.

Tomcat starts up with only the following error: bad SQL grammar [SELECT "version" FROM "DataHubVersion"]; nested exception is java.sql.SQLSyntaxErrorException: user lacks privilege or object not found: DataHubVersion in statement [SELECT "version" FROM "DataHubVersion"]

I am running HSQL.

[nicolabeghin]

I would try running DataHub with MySQL db in order to be able to have a greater degree of control over what's going on (it seems a DB issue, not a Datahub-related one)

[Slava]

Many things could cause the first issue. I suspect the self-signed certificate was added to the keystore without the -trustca option. By default, self-signed certificates are not trusted and need to be trusted explicitly during the certificate import: keytool -import ... -trustca

Second issue is also not simple to understand. I agree with Nicola that using mysql may help because it allows easily look inside the database. With hsql it can be complicated, but I suspect that table does not exist. I doubt hsql would complain about permission, if the table actually existed and was created by DataHub. Could you check the datahub.autoInitMode property setting. If it's not create-drop then the database tables won't be created