Environment: Docker version 20.10.12 , hosted by Ubuntu 22.04.1 LTS server. Linuxserver/piwigo:14.4.0
Piwigo does not really log out the user, even after the user chooses to log off by clicking the button. The result is that when you try to authenticate Piwigo using a new credencial, the application doesen´t show the keycloak login and and automatically enter the same session as before. I really appreciate any help.
Environment: Docker version 20.10.12 , hosted by Ubuntu 22.04.1 LTS server. Linuxserver/piwigo:14.4.0
Piwigo does not really log out the user, even after the user chooses to log off by clicking the button. The result is that when you try to authenticate Piwigo using a new credencial, the application doesen´t show the keycloak login and and automatically enter the same session as before. I really appreciate any help.
<!-- github-sync-id:2997299103 -->
More information... Keycloack provides an endpoint that gives instructions to the plugin.
It seems that Piwigo follows the instructions to log in, but it does not use the indicated endpoints to refresh the token, causing timeout and log out problems.
More information... Keycloack provides an endpoint that gives instructions to the plugin.
It seems that Piwigo follows the instructions to log in, but it does not use the indicated endpoints to refresh the token, causing timeout and log out problems.
<!-- github-comment-id:2807225534 -->
First of all, an official piwigo docker image will soon be available and to help the community it will be much simpler as we will have control over everything.
Secondly, regarding the Open ID Connect plugin, you're probably talking about it ‘https://github.com/jasperweyne/PiwigoOpenIdConnect’ but it isn't maintained by the piwigo team and the latest commit seems to be 4 years old. You should try to relaunch this developer to resolve the problems.
First of all, an official piwigo docker image will soon be available and to help the community it will be much simpler as we will have control over everything.
Secondly, regarding the Open ID Connect plugin, you're probably talking about it ‘https://github.com/jasperweyne/PiwigoOpenIdConnect’ but it isn't maintained by the piwigo team and the latest commit seems to be 4 years old. You should try to relaunch this developer to resolve the problems.
<!-- github-comment-id:2976661516 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Environment: Docker version 20.10.12 , hosted by Ubuntu 22.04.1 LTS server. Linuxserver/piwigo:14.4.0
Piwigo does not really log out the user, even after the user chooses to log off by clicking the button. The result is that when you try to authenticate Piwigo using a new credencial, the application doesen´t show the keycloak login and and automatically enter the same session as before. I really appreciate any help.
More information... Keycloack provides an endpoint that gives instructions to the plugin.
It seems that Piwigo follows the instructions to log in, but it does not use the indicated endpoints to refresh the token, causing timeout and log out problems.
First of all, an official piwigo docker image will soon be available and to help the community it will be much simpler as we will have control over everything.
Secondly, regarding the Open ID Connect plugin, you're probably talking about it ‘https://github.com/jasperweyne/PiwigoOpenIdConnect’ but it isn't maintained by the piwigo team and the latest commit seems to be 4 years old. You should try to relaunch this developer to resolve the problems.
Thank you for your response @LintyDev