cloudfoundry / cloudfoundry/stratos

Setting "Disable session timeout" to true in Stratos does not work

Open
#4,918 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

community
Dominant language
TypeScript
Stars
267
Forks
137
Avg merge
5h 14m
Merged PRs (30d)
77

Description

Stratos Version

4.4.0

Frontend Deployment type
  • Cloud Foundry Application (cf push)
  • Kubernetes, using a helm chart
  • Docker, single container deploying all components
  • npm run start
  • Other (please specify below)
Backend (Jet Stream) Deployment type
  • Cloud Foundry Application (cf push)
  • Kubernetes, using a helm chart
  • Docker, single container deploying all components
  • Other (please specify below)
Expected behaviour

Stratos should not timeout after logging in.

Actual behaviour

Stratos is getting timed out even after setting disabling session timeout to true

Steps to reproduce the behavior

Login to Stratos portal ( For instance : https://ui.172.16.138.138.nip.io/login || Username: admin )
CFMR-1
CFMR-2

Log output covering before error and any error statements
No error messages 
Detailed Description

Stratos is getting timed out even after disabling session timeout option.
After enabling "Disable session timeout" option. We monitored the session for 2 hours. It is getting timed out after 40-45 Minutes which is not the expected result.

Context
Possible Implementation

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or code entry points are named. Reproduce the login flow with the Docker frontend and Kubernetes Helm backend, using the reported session-timeout setting. Done means a session remains active beyond the reported 40–45 minute timeout when the setting is enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, docker, kubernetes, typescript
Domain
authentication, backend, frontend, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.