Bug #7006

[Docker] Fix SSO configuration in published images

Added by Brett Smith about 2 years ago. Updated 8 months ago.

Status:ClosedStart date:08/17/2015
Priority:NormalDue date:
Assignee:-% Done:


Target version:Arvados Future Sprints
Story points-
Velocity based estimate-


You can't log in to the API server running in our published Docker image. It's configured to use auth.curoverse.com for SSO, identifying with the SSO client name "devsandbox". However, auth.curoverse.com has no such client (instead the name is "local docker installation"). This means all authorization attempts will fail.

Peter says that the image should be set up to use a matching SSO server image, which in turn is configured with local accounts.


#1 Updated by Brett Smith about 2 years ago

  • Description updated (diff)

#2 Updated by Brett Smith about 2 years ago

As a short-term fix, I updated SSO_CLIENT_NAME in Jenkins' build configuration to match what auth.curoverse.com. That fixes the immediate bug.

#3 Updated by Tom Clegg 8 months ago

  • Status changed from New to Closed

Also available in: Atom PDF