What is happening is that, if user clicks log out, he is redirected, but not logged out, as I can browse to the restricted webpage as if i where loged in.
I’ve checked really carefully the forum and tutorial, but I can’t see any issue.
This might not be the issue cause but you should really be setting up your security provider in globals in newer versions:
In the older docs it was needed in every API action this is no longer required and after you define once in globals you just select it from there so no need to add a provider per API action just goes straight into the logout etc
Have you checked in the dev tools (browser console) in Applications and then Cookies to see if the cookie is still there when logging out? It looks like you’re setting a cookie every time you log in but that cookie should be removed when you log out.
Can you remove the security provider from the login and logout action and just use the dropdown to select the provider you defined in globals it might be nothing but could be causing a issue this thread is looking related:
Finally solved this issue: it was me: making this server connection load inside a link, so it was trying to loading the link (#) instead of the server connect. Make it a paragraph and worked fine!
- that was my first attempt.
