fix(api): use weblogin access token with API base_url redirect

[palazzem]

Related Issues

• Fixes Polling is not triggered even when there are changes #158 for a specific session token handling scenario.

Summary of Changes

This PR ensures the client consistently uses the SessionID obtained during the web login flow, regardless of whether a redirect_url is provided by the e-Connect Cloud API.

Background:
Previously, if a redirect_url was specified, the client would default to the session information derived from that redirect, leading to a situation where updates stopped being received after the first access token expired (typically within 10–20 minutes). This change addresses that problem by enforcing the use of the SessionID retrieved using the web login, thus maintaining a valid session that receives updates from the Cloud API.

How It Works:
Overrides the behavior when a redirect_url is returned, so that the session continues to rely on a session_id that is registered with the e-Connect backend, and that can consistently receive updates.

Testing

Verified manually with users configured with a redirect_url—confirmed they continue receiving updates after access token expiration and session refresh. Unittests have been added as regression tests.

Additional Notes

n/a

Checklist

• Linked issue addressed and described clearly
• Behavior verified through testing
• Code is properly documented

[coveralls]

Pull Request Test Coverage Report for Build 14539457050

Details

• 9 of 9 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 14539439977:	0.0%
Covered Lines:	417
Relevant Lines:	417

---

💛 - Coveralls