ODK Collect and OXD Setup

[Caesar]

Dear fellow users,

I am have set up openXdata from war file and and trying to get it working with ODK Collect. I have followed the steps mentioned on https://trac.openxdata.org/wiki/ODKCollect but on testing the page (http://<server_url>:443/openXdata/mpsubmit/odk/formList) , I get the page shown on the attached file. When I just login to openXdata using the URL http://<server_url>:8080/openXdata/, I am able to login to openXdata and view sample forms. Has anybody bumped onto a similar issue.

Regards,
Caesar

[Raghu Mittal]

Hi Caesar,

You have specified different port numbers i.e. 443 and 8080 in the different urls. But I am assuming that this is a typo in the email and you are probably using the right url while testing.

The error that you see when you try the link in the browser may be due to SSL not being setup correctly or it needs https to be specified. Can you give something like this and try again, i.e. use https instead of http:

https://<server_url>:443/openXdata/mpsubmit/odk/formList

Regards,

Raghu

--
You received this message because you are subscribed to the Google Groups "openXdata Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openxdata-use...@googlegroups.com.
To post to this group, send email to openxda...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openxdata-users/0e661d11-c645-4825-97be-b052480d9df6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Dagmar Timler]

Raghu's advice is good. 

My comment is that sometimes when a browser renders XML it omits all XML tags. In that case you would see only the form names (and would need to view the source of the page to see the XML). If your form names were using a different charset, then you may very well see something like the attached screenshot and it would be working correctly!

To view this discussion on the web visit https://groups.google.com/d/msgid/openxdata-users/CALwKaxq_MbJYwDe4dzvc0hV0XjzNpy7_60KdvamBywVvy1AudQ%40mail.gmail.com.

[Caesar]

Thanks Raghu,

Funny enough, if I use the URL as https://<server_url>/openXdata/,  I am able to login to openXdata but using http://<server_url>:443/openXdata/ brings the same error as shown in the previous screen shot. Browsing to

https://<server_url>/openXdata/mpsubmit/odk or http://<server_url>:8880/openXdata/mpsubmit/odk show a 404 error. Sorry about the previous typo I had configured the tomcat server to listen to port 8880. Could this be a certificate issue as you mentioned. I am using a self signed certificate for testing purposes before implementing this in a production environment so judged that I might need the CA certified certificate once ready to deploy project to production.

Regards,

Caesar

[Caesar]

Thanks Dagmar,

Would then suggest/advice an SSL certificate regeneration before trying again then?

Regards,
Caesar

[Dagmar Timler]

Personally I'd advise going without a self-signed certificate - test with the 8443 or 443 ports as described in the oXd documentation, and then when you are satisfied with the oXd ODK bridge just take the plunge and purchase a certificate. My experience with self-signed certificates has never been great - you need to manually add them to the Java keystore in order to have them automatically recognized or otherwise bypass all the nice security given with SSL. I have never tested oXd with a self-signed certificate to see how it would work with the emulator. It wouldn't work with a phone until you manually add it to the keystore.

However, having said all that, if you can't even login to the Dashboard using SSL, you may wish to check how you did your certificate creation and installation. Maybe try these instructions? https://www.sslshopper.com/article-how-to-create-a-self-signed-certificate-using-java-keytool.html

To view this discussion on the web visit https://groups.google.com/d/msgid/openxdata-users/68dae69e-7c53-4b8c-a37d-3f6fdc0d3ab5%40googlegroups.com.

[Dagmar Timler]

Also, please take note of the latest "Poodle" venerability with SSL. Here is some more information with the correct Tomcat configuration: https://access.redhat.com/solutions/1232233