Thanks @Jluc for the error message (received privately), it gave me the answer: the site only shows the index page if you access it through its menu, and the integration opened it directly, so the page arrived empty.
This is fixed in 1.1.1: update from Gladys, then click again on Test the connection and fetch now. No need to delete the integration this time
On avance @Jluc! This message just means that the integration is still set to cookie, and a session cookie only lasts a few hours. Since your password connection works, it’s the simplest: in the settings, choose email and password login, re-enter them, save, then run Test the connection and check now.
(And yes, this message should have been displayed in red rather than green, I’ll fix that at the same time )
I just installed the integration and I have the same issue
Here are the logs:
[2026-11-08T22:18:43.287Z] [INFO] [ista] Signed in to the ista portal
[2026-11-08T22:18:43.367Z] [WARN] [sync] Sign-in to the ista portal failed (session_expired): the portal still asks to sign in after a successful login
[2026-11-08T22:18:43.371Z] [INFO] [ista] Connection test: failed (status_session_expired)
Thanks @prohand for the logs, they help a lot! The connection succeeds, but when the integration then opens the index page via the menu, the portal asks for a login again, and I still don’t see why.
The 1.1.3 now shows in the logs which page the portal redirects to and why (address without its parameters, nothing personal). Can you update, restart Test Connection and then Check Now and paste the line [WARN] [sync] … for me?
And if you have two minutes on the browser side: connected to the site, F12, Network tab, filter Document, then click on Index on Demand in the menu. The names of the lines that appear, in order (menu.do?id=…, then…), will tell me exactly the path the site follows.
@Jluc: same for you if you can, with the email and password login.
[2026-11-09T08:55:22.296Z] [INFO] Starting the ista Web’conso integration...
[2026-11-09T08:55:22.745Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:80)
[2026-11-09T08:55:38.168Z] [INFO] [ista] Signed in to the ista portal
[2026-11-09T08:55:38.247Z] [WARN] [sync] Sign-in to the ista portal failed (session_expired): the portal still asks to sign in after a successful login (public page at ista-webconso.fr/espace-client-v2/public/home.do, HTTP 200)
[2026-11-09T08:55:38.251Z] [INFO] [ista] Connection test: failed (status_session_expired)
When I filter on Document in the network tab, I get nothing
Thanks @prohand, the line is clear: right after the connection, the entry for the « On-Demand Index » menu redirects the integration to the public homepage, as if it were not connected. The site therefore requires something that the browser does and not the integration.
Two quick tests to find out what:
Connected to the site in your browser, paste this address in the address bar and validate: https://www.ista-webconso.fr/espace-client-v2/menu.do?id=lgtOcc_index. Do you arrive on the index page, or on the homepage?
For the Network tab, first check Preserve log (Conserver le journal), otherwise the list is cleared with each page change. Then, filter Document, click on On-Demand Index in the menu, and give me the names of the lines in order.
Thanks to both of you, your tests have unlocked everything!
@prohand, your test is the key: even when connected, the menu address pasted as-is redirects to the home page and role selection. The site only accepts the entry « Index on Demand » from the dashboard of the resident, like when you click in the menu. The integration went directly there.
The 1.1.4 now goes through the dashboard, then through the menu, like a click. To test: update from Gladys, then Test the connection and check now.
@Jluc, for you the red message « expired cookie » means the configuration is still in cookie mode: in the connection method selection, choose email and password, then save.
If it still gets stuck, paste me the line [WARN] [sync] from the logs: it now shows which page the site redirects to.
[2026-11-09T11:04:09.373Z] [INFO] Starting the ista Web’conso integration...
[2026-11-09T11:04:09.614Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:80)
[2026-11-09T11:04:16.615Z] [INFO] [ista] Signed in to the ista portal
[2026-11-09T11:04:16.814Z] [WARN] [sync] Sign-in to the ista portal failed (session_expired): the portal still asks to sign in after a successful login (public page at ista-webconso.fr/espace-client-v2/public/home.do, HTTP 200)
[2026-11-09T11:04:16.819Z] [INFO] [ista] Connection test: failed (status_session_expired)
I also get this message even if I use the email/password:
Thanks @prohand! Your line shows that the session is lost immediately after logging in, even through the dashboard. I found a much more likely cause: the site responds to both ista-webconso.fr and www.ista-webconso.fr. After logging in, it redirects you to the address with www and deposits its session cookie there, then the integration continued on the address without www, without that cookie. So for the site, it was no longer connected. That’s also why the cookie mode worked.
The 1.1.5 shares the session between the two addresses. Update from Gladys, then Test the connection and check now
[2026-11-09T12:02:16.657Z] [INFO] Starting the ista Web’conso integration...
[2026-11-09T12:02:16.926Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:80)
[2026-11-09T12:02:25.072Z] [WARN] [sync] Sign-in to the ista portal failed (session_expired): the sign-in ended on the public page ista-webconso.fr/espace-client-v2/public/loginIpmp.do: no session kept
[2026-11-09T12:02:25.076Z] [INFO] [ista] Connection test: failed (status_session_expired)
@prohand, your line loginIpmp.do was the right one: it’s ista’s internal error page. Its session cookie is protected so that it is not sent back after returning from ista’s login page. A browser respects this rule, and the site then opens a new session. The integration, however, was sending the cookie, and the site was crashing.
@Jluc, your screenshot shows another flaw: in password mode, the error incorrectly mentioned an « expired cookie ». Your setting was therefore correct, it was the message that was wrong.
The 1.1.7 fixes both. Update from Gladys, then Test the connection and check now. And if it still doesn’t work, the line [WARN] [sync] will tell me where
Thanks @Jluc, the message is finally correct The portal accepts your password, but doesn’t keep the session afterwards. To know at which step, I need the line [WARN] [sync] … from the integration logs.
@prohand, can you run the test again in 1.1.7 and paste that line as usual? It will tell us on which page the portal is now dropping us after the cookie fix.