Customizable Tower login timeout
acknowledged
W
Wenge Boa
I noticed that my Enterprise tower instance logs me out much faster than tower.nf does. Is there a setting that controls the timeout value for logins and can this be increased so that we don't need to log in as often?
W
Wenge Boa
I tried the provided solution of setting the access-token expiration to 2 hours, but unfortunately this also seems to control the tokens that are used by running pipelines. All of my pipelines were failing after 2 hours with this error: "WARN: Unexpected HTTP response.
Failed to send message to https://nextflow.int.janelia.org/api -- received
- status code : 404
- response msg: Not Found
- error cause : Not Found"
Rob Newman
acknowledged