Bug #17224
closed
login-sync needs to issue tokens from logincluster
100%
Description
Login sync issues tokens created by the local cluster.
As a short term solution, add feature for providing alternate host/token for the login cluster, so we issue tokens from
the login cluster instead.
In other words, get the virtual machine list from the local cluster, but issue tokens from the login cluster.
The environment variables are LOGINCLUSTER_ARVADOS_API_HOST and LOGINCLUSTER_ARVADOS_API_TOKEN.
The longer term solution is to make the token management API more federation aware.
Updated by Peter Amstutz almost 4 years ago
- Status changed from New to In Progress
Updated by Peter Amstutz almost 4 years ago
- Related to Bug #17225: Ruby SDK cannot connect to multiple clusters added
Updated by Peter Amstutz almost 4 years ago
17224-login-sync @ f53363ea4642dd165decc6786b835979a1dc9f73
Updated by Peter Amstutz almost 4 years ago
- Subject changed from login sync problem with logincluster to login-sync needs to issue tokens from logincluster
Updated by Lucas Di Pentima almost 4 years ago
AFAICT the envvars LOGINCLUSTER_ARVADOS_API_HOST & LOGINCLUSTER_ARVADOS_API_TOKEN are new and not mentioned anywhere. Do you think it would be necessary to write some documentation about them?
Updated by Peter Amstutz almost 4 years ago
- Target version changed from 2021-01-06 Sprint to 2021-01-20 Sprint
Updated by Peter Amstutz almost 4 years ago
Lucas Di Pentima wrote:
AFAICT the envvars
LOGINCLUSTER_ARVADOS_API_HOST&LOGINCLUSTER_ARVADOS_API_TOKENare new and not mentioned anywhere. Do you think it would be necessary to write some documentation about them?
Added to shell server install doc.
17224-login-sync @ a622b6980539db9563b6a92e0996197b61dae862
Updated by Peter Amstutz almost 4 years ago
- Status changed from In Progress to Resolved