2 Replies Latest reply on Dec 6, 2016 3:53 AM by Mirko Swillus

    Jive Daily Hosted on Jive9 OnPrem

    Mirko Swillus

      Dear Jivers,

       

      I just finished the setup of a Jive9 OnPrem Demo sandbox on our own infrastructure. Now I want to test Jive Daily Hosted, but the jive daily hosted App on my iOS device is complaining about "my organization is not enabled for Jive Daily".

       

      What I've done so far:

      • Installed Jive9 OnPrem Employer Edition (jive_sbs_employee-9.0.0.0.el7.x86_64.rpm)
      • Enabled AddOns
      • Changed the time out tokens for both apps (Android and iOS) under https://<jive-url>/addon-services!input.jspa
      • Checked that https://<jive-url>/admin/mobile.jspa looks good
      • Downloaded the jive daily hosted app from the iOS Appstore to my iOS device

       

      The effect is as follows:

      • When I open up the iOS App, it prompts me to insert the jive URL, I'm typing the jiveURL
      • It then shows a spinner and prints a message that says that my organization is not enabled for Jive Daily (german locale, so this is maybe not the strict wording)
      • On the Access-Logs of my instance I'm seeing the following requests:
        xxx.xx.xx.xxx - - [05/Dec/2016:18:26:28 +0100] "GET /api/version HTTP/1.1" 200 245 0 0 "-" "jive-daily/1.0.0 ios" "application/json" - xxx.xx.xx.xxx - - [05/Dec/2016:18:26:29 +0100] "GET /api/addons/fde78d67-01d1-4c57-ba7f-4ee3c94234ab/session-grant-allowed HTTP/1.1" 200 40 0 0 "-" "jive-daily/1.0.0 ios" "application/json" - 
      • When I look at the response body it says this:
        $ curl -i https://<jive-url>/api/addons/fde78d67-01d1-4c57-ba7f-4ee3c94234ab/session-grant-allowed HTTP/1.0 200 Connection established HTTP/1.1 200 OK Date: Mon, 05 Dec 2016 17:07:22 GMT Server: Apache X-Jive-Request-Id: 49525400-bb0d-11e6-8aa7-00505610a00f X-Jive-Flow-Id: 49525401-bb0d-11e6-8aa7-00505610a00f X-Frame-Options: SAMEORIGIN P3P: CP="CAO PSA OUR" Content-Type: application/json Expires: Mon, 05 Dec 2016 17:07:22 GMT Vary: Accept-Encoding,User-Agent Cache-Control: no-store, no-cache, must-revalidate, private, max-age=0 X-JSL: D=8669 t=1480957642047241 Set-Cookie: jive.login.ts=1480957642048; Path=/; HttpOnly Set-Cookie: jive.security.context=nss1jGxA4nxr9kmv6zmtAv//////////rTqu1HcFPvFEOOnE0KkG+FKs80DKzzXepnkCFhVqE1owhdENXlahnrliSd79+1XgtVaCatRhgHq2qHaraNNO56nqIzLeaDrF; Path=/; HttpOnly Connection: close Transfer-Encoding: chunked {   "status" : 404 } 

       

      So status is 200, but response body contains a json status 404.

       

      So I really don't understand why the app is trying to connect to an add on with a static UUID. It seems it was only made for the cloud instance, where this add on UUID is maybe static. But shouldn't that thing also connect to Jive OnPrem environments?

       

      Any hint is very much appreciated, since I'm very keen on testing Jive Daily. Thanks in advance,

      Mirko