api-session-timeout chrome block issue

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

api-session-timeout chrome block issue

Adrian Owen

I set api-session-timeout to 2 minutes

 

Catalina out shows message:   Sessions will expire after 2 minutes of inactivity.

 

I access Guacamole URL with Chrome browser, and  it is blocked by Chrome, never appears.

 

 

I wait over 2 minutes, but no timeout occurs.

 

Should block trigger timeout?

 

 

Thanks, Adrian

 

Reply | Threaded
Open this post in threaded view
|

Re: api-session-timeout chrome block issue

vnick
On Mon, Oct 12, 2020 at 8:33 AM Adrian Owen <[hidden email]> wrote:

I set api-session-timeout to 2 minutes

 

Catalina out shows message:   Sessions will expire after 2 minutes of inactivity.

 

I access Guacamole URL with Chrome browser, and  it is blocked by Chrome, never appears.


What do you mean "blocked by Chrome"?
 

 

 

I wait over 2 minutes, but no timeout occurs.

 

Should block trigger timeout?

 


No, the "block" will not trigger a timeout.  What is important as to whether the timeout occurs or not is any API activity.  As the property states, it is the timeout for the API session.  So, while I'm not sure what you mean by "blocked by Chrome", if there is *any* API activity at all during this 2-minute period, the timeout will not occur and the session will remain active.

-Nick
Reply | Threaded
Open this post in threaded view
|

RE: api-session-timeout chrome block issue

Adrian Owen

Hi Nick,

 

What do you mean "blocked by Chrome"?

 

I use JSON Auth API, and my Web application send JSON and receives AuthToken,

 

Next I open the Guacamole URL+AuthToken in new browser window.

 

But first time on Chrome, the popup blocker, blocks the guacamole window.

 

Same Chrome behaviour can be seen here: http://popuptest.com/

 

 

Adrian

 

 

 

 

 

 

 

From: Nick Couchman [mailto:[hidden email]]
Sent: 12 October 2020 15:14
To: [hidden email]
Subject: Re: api-session-timeout chrome block issue

 

On Mon, Oct 12, 2020 at 8:33 AM Adrian Owen <[hidden email]> wrote:

I set api-session-timeout to 2 minutes

 

Catalina out shows message:   Sessions will expire after 2 minutes of inactivity.

 

I access Guacamole URL with Chrome browser, and  it is blocked by Chrome, never appears.

 

What do you mean "blocked by Chrome"?

 

 

 

I wait over 2 minutes, but no timeout occurs.

 

Should block trigger timeout?

 

 

No, the "block" will not trigger a timeout.  What is important as to whether the timeout occurs or not is any API activity.  As the property states, it is the timeout for the API session.  So, while I'm not sure what you mean by "blocked by Chrome", if there is *any* API activity at all during this 2-minute period, the timeout will not occur and the session will remain active.

 

-Nick

Reply | Threaded
Open this post in threaded view
|

Re: api-session-timeout chrome block issue

vnick
On Mon, Oct 12, 2020 at 10:56 AM Adrian Owen <[hidden email]> wrote:

Hi Nick,

 

What do you mean "blocked by Chrome"?

 

I use JSON Auth API, and my Web application send JSON and receives AuthToken,

 

Next I open the Guacamole URL+AuthToken in new browser window.

 

But first time on Chrome, the popup blocker, blocks the guacamole window.

 


In that case, whether or not the API timeout is effective is going to depend upon whether there is any other traffic that would keep that session alive.  I do not know the internals of how Chrome's popup blocker works, but it is possible that Chrome is hiding the actual window while still beginning to load parts of the page or keep the session active with the server on the chance that you'll want to allow the pop-up and continue.  Again, I don't know this for sure, it's just my speculation on what might be going on - you'll have to investigate further in Chrome.

Also, when you changed the API session timeout property in guacamole.properties, did you reload the web application (restart Tomcat or re-deploy Guacamole)?

-Nick
Reply | Threaded
Open this post in threaded view
|

RE: api-session-timeout chrome block issue

Adrian Owen

Hi Nick,

 

After setting api-session-timeout, I restarted Guacamole server.

 

>>it is possible that Chrome is hiding the actual window while still beginning to load parts of the page or keep the session active with the server

 

I have recording enabled on session. But during site block, there is no recording file.

So no parts of page have been loaded during block

 

As soon as I allow block, Guacamole window pops up, and recording file appears and starts appending with data.

 

Maybe block happens before guacamole starts processing, hence no timeout?

 

 

Kind Regards,

Adrian Owen | CTO | ForestSafe SessionSafe LAPSafe | PPM PAM | EESM 

 

From: Nick Couchman [mailto:[hidden email]]
Sent: 13 October 2020 11:42
To: [hidden email]
Subject: Re: api-session-timeout chrome block issue

 

On Mon, Oct 12, 2020 at 10:56 AM Adrian Owen <[hidden email]> wrote:

Hi Nick,

 

What do you mean "blocked by Chrome"?

 

I use JSON Auth API, and my Web application send JSON and receives AuthToken,

 

Next I open the Guacamole URL+AuthToken in new browser window.

 

But first time on Chrome, the popup blocker, blocks the guacamole window.

 

 

In that case, whether or not the API timeout is effective is going to depend upon whether there is any other traffic that would keep that session alive.  I do not know the internals of how Chrome's popup blocker works, but it is possible that Chrome is hiding the actual window while still beginning to load parts of the page or keep the session active with the server on the chance that you'll want to allow the pop-up and continue.  Again, I don't know this for sure, it's just my speculation on what might be going on - you'll have to investigate further in Chrome.

 

Also, when you changed the API session timeout property in guacamole.properties, did you reload the web application (restart Tomcat or re-deploy Guacamole)?

 

-Nick

Reply | Threaded
Open this post in threaded view
|

Re: api-session-timeout chrome block issue

vnick
On Tue, Oct 13, 2020 at 7:05 AM Adrian Owen <[hidden email]> wrote:

Hi Nick,

 

After setting api-session-timeout, I restarted Guacamole server.

 

>>it is possible that Chrome is hiding the actual window while still beginning to load parts of the page or keep the session active with the server

 

I have recording enabled on session. But during site block, there is no recording file.

So no parts of page have been loaded during block

 

As soon as I allow block, Guacamole window pops up, and recording file appears and starts appending with data.

 

Maybe block happens before guacamole starts processing, hence no timeout?


Yes, this is possible, too - if a session is being initiated, then you should see a message indicating that the login has succeeded in the Tomcat logs.

-Nick