Accès public à GeoNature - Lien ne fonctionne pas au premier chargement #3353
Labels
Comments
VincentCauchois
added a commit
that referenced
this issue
Feb 4, 2025
Several fixes: - Fix direct public access with query param when INPN CAS authentification is configured - [WIP] Fix flaky login and logout // ref #3353
VincentCauchois
added a commit
that referenced
this issue
Feb 4, 2025
Several fixes: - Fix direct public access with query param when INPN CAS authentification is configured - [WIP] Fix flaky login and logout // ref #3353
VincentCauchois
added a commit
that referenced
this issue
Feb 4, 2025
Several fixes: - Fix direct public access with query param when INPN CAS authentification is configured - [WIP] Fix flaky login and logout // ref #3353
VincentCauchois
added a commit
that referenced
this issue
Feb 4, 2025
Several fixes: - Fix direct public access with query param when INPN CAS authentification is configured - [WIP] Fix flaky login and logout // ref #3353 - Use AuthGuard rather than UserCasGuard on NavHomeComponent, and remove UserCasGuard definition - Handle the case where a user is no more authentified server-side but still authentified client-side, by calling frontend logout() Chore: - Remove unused Router and AuthService from ModuleService constructor
VincentCauchois
added a commit
that referenced
this issue
Feb 4, 2025
Several fixes: - Fix direct public access with query param when INPN CAS authentification is configured - [WIP] Fix flaky login and logout // ref #3353 - Use AuthGuard rather than UserCasGuard on NavHomeComponent, and remove UserCasGuard definition - Handle the case where a user is no more authentified server-side but still authentified client-side, by calling frontend logout() Chore: - Remove unused Router and AuthService from ModuleService constructor
VincentCauchois
added a commit
that referenced
this issue
Feb 5, 2025
Several fixes: - Fix direct public access with query param when INPN CAS authentification is configured - Fix flaky login and logout - ref #3353 - Use AuthGuard rather than UserCasGuard on NavHomeComponent, and remove UserCasGuard definition - Handle the case where a user is no more authentified server-side but still authentified client-side, by calling frontend logout() Chore: - Remove unused Router and AuthService from ModuleService constructor
VincentCauchois
added a commit
that referenced
this issue
Feb 5, 2025
Several fixes: - Fix direct public access with query param when INPN CAS authentification is configured - Fix flaky login and logout - ref #3353 - Use AuthGuard rather than UserCasGuard on NavHomeComponent, and remove UserCasGuard definition - Handle the case where a user is no more authentified server-side but still authentified client-side, by calling frontend logout() Chore: - Remove unused Router and AuthService from ModuleService constructor
VincentCauchois
added a commit
that referenced
this issue
Feb 6, 2025
Several fixes: - Fix direct public access with query param when INPN CAS authentification is configured - Fix flaky login and logout - ref #3353 - Use AuthGuard rather than UserCasGuard on NavHomeComponent, and remove UserCasGuard definition - Handle the case where a user is no more authentified server-side but still authentified client-side, by calling frontend logout() Chore: - Remove unused Router and AuthService from ModuleService constructor
Christophe-Ramet
pushed a commit
that referenced
this issue
Feb 6, 2025
Several fixes: - Fix direct public access with query param when INPN CAS authentification is configured - Fix flaky login and logout - ref #3353 - Use AuthGuard rather than UserCasGuard on NavHomeComponent, and remove UserCasGuard definition - Handle the case where a user is no more authentified server-side but still authentified client-side, by calling frontend logout() Chore: - Remove unused Router and AuthService from ModuleService constructor
|
Résolu dans #3355 grâce au travail de @VincentCauchois ( voir #3360) |
16 tasks
|
Correction intégrée dans la 2.15.3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
Version 2.15.2
Testé aussi sur 2.13.4
Description du bug
Pour accéder à GeoNature avec un lien public, la page doit être chargée deux fois pour que login "public" puisse être pris en compte.
Comportement attendu
ARriver directement sur laapage
Comment reproduire
our reproduire, on peut ouvrir un onglet d'un chrome-like en navigation privée, et ouvrir l'accès public sur la demo:
https://demo.geonature.fr/geonature/#/?access=public
Et on tombe sur une page blanche avec redirection sur https://demo.geonature.fr/geonature/#/, qu'il faut recharger pour que la connection se passe
The text was updated successfully, but these errors were encountered: