we allow get requests to the jwt controller
we allow get requests to the jwt controller

I tried adding a spec test for this, but the controller specs don't go through the router
And it doesn't seem worthwhile to add a routing spec just for this one file when
the router is so sparsely covered already.
Ideally this will be covered by one of the upcoming cypress integration tests which
are going to try launching the activity-player from the portal.

concord-consortium/rigse,concord-consortium/rigse,concord-consortium/rigse,concord-consortium/rigse,concord-consortium/rigse,concord-consortium/rigse