Endpoint disconnect ("We've been having trouble communicating with Cloud Foundry")

Frontent Deployment type

• Cloud Foundry Application (cf push)
• Kubernetes, using a helm chart
• Docker, using docker compose
• Docker, single container deploying all components
• npm run start
• Other (please specify below)

Backend (portal-proxy) Deployment type

• Cloud Foundry Application (cf push)
• Kubernetes, using a helm chart
• Docker, using docker compose
• Docker, single container deploying all components
• Other (please specify below)

Stratos 2.0.0-rc1 with pre SCF-2.11.0-rc1 on CaaSPv3-GM

Expected behaviour

The UI should either keep the session active until the user logs out, or redirect to the login page after a default session timeout.

Actual behaviour

When the UI isn’t touched for a while the following error will be shown:

“We’ve been having trouble communicating with Cloud Foundry - You may be seeing out-of-date information”

Steps to reproduce the behavior

Log in to Stratos as admin, and leave the browser window open (idle) for a while (~10 min.). Then try to reuse the UI.

Log output covering before error and any error statements

"We've been having trouble communicating with Cloud Foundry - You may be seeing out-of-date information"

When I “Logout” and “Login” it works again, but will also loose communication after a while again.

Looks like the session times out by default, but the user isn’t redirected to the login page. Instead the error message is shown.

[svollath]

Like mentioned in a comment before already the relation to session timeouts was wrong. I reproduced it with 2.0.0-rc2 as well, and even when it’s disconnected, the session will time out and redirect as expected.

So the issue is about loosing communication to cloud foundry under UI usage - the proxy container logs “Couldn’t refresh token for CNSI”.

[irfanhabib]

Some more detail from @svollath

yes, it exactly happend now with RC2 - the deployment succeeded 20 min. ago and I was logged in for maybe 10-15 min. - I just let "Cloudfoundry"-"Firehose" run, and the switched to "Applications" after ~10min.. It could be that it's triggered by switching to another menu after a while.

Irfan Habib @IHabib 2:58 PM
ok I'll keep that in mind when testing
thanks

Sebastian Vollath @svollath 3:02 PM
... and btw. when it's in that state (Communication Error) - then, after another while "Are you still there" and redirect to the login page will both work. So in fact my initial thought is wrong. So feel free to change the title of that issue ...

Irfan Habib @IHabib 3:03 PM
So basically...
1. The redirect works when the `Are you still there` message pops up
2. What doesn't work is: there is an endpoint error (red bar) when you perform some operations after soem time?
is this correct?

Sebastian Vollath @svollath 3:06 PM
Yes, that's what I got from Friday - when I just left the UI from reproducing, I saw a "Are you still there" dialog, as well as it was back to the login page - but I mean that must have happened more than an hour later ...