Upon automated logout the D8 version of the module forces a single destination:
http://www.example.com/admin/config/people/autologout
Redirect URL at logout set to "/"

Before logout:
https://www.example.com/admin/config/people/autologout

After logout:
https://www.example.com/?destination=/admin/config/people/autologout&tim...

One possible use case would be to redirect automatically to the page they are on just in an unauthenticated way.
Pages with no anonymous access would of course be 403 forbidden as expected.

However, if visitors or users were on a specific page such as:
https://www.example.com/node/1

They would remain on the page like so:
https://www.example.com/node/1&timeout=1

Question: was this the intention of "Use alternate logout method"?

Side note, minor type in that section:
"Normally when auto logout is triggered, it is done via an AJAX service call. Sites that use an SSO provider, such as CAS, are likely to see this request fail with the error "Origin is not allowed by Access-Control-Allow-Origin". The alternate appraoch is to have the auto logout trigger a page redirect to initiate the logout process instead."

Comments

worldlinemine created an issue. See original summary.

worldlinemine’s picture

Version: 8.x-1.0-beta1 » 8.x-1.0-rc1
DeaOm’s picture

Version: 8.x-1.0-rc1 » 8.x-1.x-dev
Status: Active » Closed (outdated)

Hi @worldlinemine. Is this still active/relevant?
I'm testing it out with the dev version of the module (1.x-dev) and if I'm understanding you correctly if you enter the slash (/) in the automated logout settings under Redirect URL at logout, you expect the user to stay on the same page as when the redirect happened. This is currently working like that in the dev version. So if a user is on a http://www.example.com/node/1 page after the automated logout happens the user is redirected to http://www.example.com?destination=/node/1&autologout_timeout=1
I also tested with different URLs, like node/2 and aliases and it works as designed.
The minor typo is also corrected in the dev version.
So because the issue is almost 4 years old, I'm closing it as outdated. You can re-open this issue or create a new one if what you had in mind is not working as expected in the dev version of the module.