invalid permissions given when a user has valid permissions when queried through a sessionless web service

[nathandunn]

ITs because the user is not in the database and the user is not an instructor.

I don't think there is a side-effect right now, but this should be an easy fix.

          if ((!userOrganismPreference || !permissionService.hasAnyPermissions(currentUser)) && !permissionService.isUserBetterOrEqualRank(currentUser, GlobalPermissionEnum.INSTRUCTOR)) {
                userObject.put(FeatureStringEnum.ERROR.value, "You do not have access to any organism on this server.  Please contact your administrator.")

curl 'http://demo.genomearchitect.org/Apollo2/user/checkLogin' \
   -H 'Content-Type: application/json' \
   -X POST \
   -d '{"username":"demo@demo.com","password":"demo"}'

The response looks like this:

{
  "firstName":"Demo",
  "lastName":"User",
  "role":"USER",
  "error":"You do not have access to any organism on this server.  Please contact your administrator.",
  "userId":16,
  "organismPermissions":[
    {
      "organism":"Honeybee",
      "permissions":"[\"WRITE\",\"EXPORT\",\"READ\"]",
      "permissionArray":[
        "WRITE",
        "EXPORT",
        "READ"
      ],
      "id":153217,
      "userId":16
    },
    {
      "organism":"Yeast",
      "permissions":"[\"WRITE\",\"EXPORT\",\"READ\"]",
      "permissionArray":[
        "WRITE",
        "EXPORT",
        "READ"
      ],
      "id":153219,
      "userId":16
    },
    {
      "organism":"Human-Hg38",
      "permissions":"[\"WRITE\",\"EXPORT\",\"READ\"]",
      "permissionArray":[
        "WRITE",
        "EXPORT",
        "READ"
      ],
      "id":153218,
      "userId":16
    },
    {
      "organism":"Yeast 4asdfasdfasdfasfdasdf asdf asdfasdfasdf",
      "permissions":"[\"WRITE\"]",
      "groupId":185085,
      "id":285564
    },
    {
      "organism":"Fictitious",
      "permissions":"[\"WRITE\"]",
      "permissionArray":[
        "WRITE"
      ],
      "id":248994,
      "userId":16
    }
  ],
  "has_users":true,
  "username":"demo@demo.com"
}