Project

General

Profile

Actions

Bug #7006

closed

[Docker] Fix SSO configuration in published images

Added by Brett Smith over 8 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Docker
Target version:
-
Story points:
-

Description

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.

Actions #1

Updated by Brett Smith over 8 years ago

  • Description updated (diff)
Actions #2

Updated by Brett Smith over 8 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.

Actions #3

Updated by Tom Clegg about 7 years ago

  • Status changed from New to Closed
Actions #4

Updated by Tom Morris about 5 years ago

  • Target version deleted (Arvados Future Sprints)
Actions

Also available in: Atom PDF