-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Armadillo doesn't seem to adhere to session timeout of 30 min #121
Comments
Weird. We set |
I think this could be due to the fact that when something goes wrong in the analysis the session is terminated. This works as intended. We need to harvest the error messages and feed it back to the DataSHIELD team. |
We speculate this is part of the Jupyter issue |
According to (use add blocker) https://www.baeldung.com/servlet-session-timeout
HttpSession session = request.getSession();
session.setMaxInactiveInterval(10*60); |
TestsIs this lines to look for?
|
Session checks seems to occur each minute ...
print found lines + 5 After so catching End expire sessions
|
It seems reproducible but is still uncertain calling increasing ds.Lasso_CVInSite(
X = "x_mat",
Y = "y_mat",
type = "regress",
nlambda = 2,
lam_ratio = 0.01,
datasources = conns,
nDigits = 4,
nfolds = 2) https://github.com/transbioZI/dsMTLClient/blob/main/R/ds.Lasso.R |
I've investigated this further and this particular time-out issue was not affected/resolved by changing |
However it has now been resolved by increasing the JWT token duration on the authentication server. Dick has set this to 4 hours, and the following now completes:
|
We now need to refresh the JWT token from within Armadillo. |
I looked at this a while ago, it appeared the changes needed are relatively easy. If the JWT needs refreshing the http(s) request will return a particular http status code, the JWT can be refreshed using the appropriate function, and the request reissued with the new JWT. If memory serves only very few places in the code need to be changed. |
Follow up issue is #669 |
How to reproduce:
Log in via Elixir and wait for 15 mins, and the session times out.
The text was updated successfully, but these errors were encountered: