Issues with UDOIT test deloyment to heroku

[ordwaye]

I so I have tried to set this up a couple times with both the instant heroku version and the cli version setting my own keys.  In both cases I am getting and error of

BLTI not valid: our key:  XXXXXX

when I actual try to access it from our test canvas site.  Is there some common setup issue that I messing up that would cause this?

[ordwaye]

Ok here is what I have figured out so far.  The first pass at creating the BLTI works and sets things up but nothing is stored in the session.  Then after being bounced to back to the canvas to authorize UDOIT to act as you and returned to UDOIT.  At that point building the BLTI $context fails when it tries to find the setup in the session because it was configured to not store anything.

I am confused as to why this should work as it really does not look like it should.

[ordwaye]

Ok next bit (made a ticket for this on github)

From leaving a trail of breadcrumb error_log's through the code it does not seem to be setting anything in the session durning /public/oauth2response.php setup. This means userid/api is not saved to the database and the rest fails.

[tr_jbates]

For those that are interested in this question, we're discussing it in the GitHub project:  Is anyone successfully testing this on heroku? · Issue #120 · ucfcdl/UDOIT · GitHub

When we have a solution, we will post it here.

[tr_jbates]

This issue has been resolved.  The problem was that the Heroku database setup code was inconsistent with recent changes to the report saving code.  There was a data-type mismatch, so it was trying to save a timestamp in a bigint field.  Thanks to Cooper Fellows (I couldn't find him in the Canvas Community), the Heroku code was updated and  @ordwaye ​ fixed his database setup accordingly.

[tr_jbates]

 @ordwaye ​ Would you mind marking this question as answered?

[Stef_retired]

If you're participating in this discussion, you'll definitely want to RSVP to the CanvasLIVE event UDOIT Installation which is coming up this Monday, December 5, 2016. RSVP “yes” if you will be there--and if you’re interested, but your schedule doesn’t allow you to attend in real time, RSVP "no" or "maybe" to receive all event updates. Your RSVP ensures that you will receive a notification should the event be cancelled or changed.