The Octime connection that fails without an actionable message remains one of the most frequent irritants in time management. The problem almost always goes beyond a simple forgotten password: corrupted SSO token, network filtering, persistent browser cache, or disabled account on the directory side. Here are seven targeted interventions, categorized by technical layer, to restore access without waiting for publisher support.
1. Purge the expired SSO token in the browser
Further reading : How to Easily Find SDMO Spare Parts for Your Generator
Since the gradual switch to SSO authentication (Microsoft Entra, Google Workspace, internal IdP), most silent blocks come from an expired or corrupted authentication token stored in the browser. Octime does not return any explicit error: the page redirects in a loop to the organization’s login screen.
We recommend specifically deleting cookies from the Octime domain and that of the IdP (login.microsoftonline.com, accounts.google.com) rather than clearing the entire cache. On Chrome, go to chrome://settings/cookies/detail to target the relevant domains. A complete restart of the browser (not just a simple tab refresh) is necessary to force the regeneration of the token.
Recommended read : Married: what name to choose for your plane ticket to avoid issues?
When looking for solutions for the blocked Octime connection, this targeted cleaning resolves most redirection loops without affecting other active sessions.
2. Check the account status in the Azure AD or Google Workspace directory
A disabled or suspended account on the directory side blocks the Octime connection without any feedback from the application. This case particularly affects temporary workers, contractors, and employees at the end of their assignments whose accounts are automatically disabled by GDPR policies for scheduled deletion.
The HR manager or IT administrator must check in the IdP console that the account is indeed active, that the associated license has not been revoked, and that MFA (multi-factor authentication) has been properly enrolled. An unvalidated MFA during the initial provisioning produces exactly the same symptom as an incorrect password.
3. Bypass network filtering and corporate proxy
IT departments are tightening network filtering (proxy, filtered DNS, ZTNA/SASE architectures). Octime in SaaS mode requires several domains to be allowed, not just the main login URL. Calls to SSO authentication servers and the application’s CDNs must also pass.
To diagnose a network blockage:
- Test the connection from a mobile network (tethering) to isolate the problem on the corporate network
- Check the proxy logs to see if requests to the Octime domains and the IdP are blocked or redirected
- Ensure that intermediate SSL certificates are not intercepted by overly aggressive TLS inspection
If access works on 4G but not on the internal network, the problem is confirmed on the infrastructure side. The network administrator will need to add the Octime domains to the proxy whitelist.
4. Reset the password via the Octime support portal (Jira Service Management)
Octime has migrated its customer support to Jira Service Management. The procedure for first logging into the support portal differs from a simple “forgot password” process. You need to click on “Continue with an Atlassian account,” then select “You can’t log in” to initiate the reset.
This step traps many users who try to log in with their usual Octime credentials on the Atlassian portal. The two authentication systems are distinct. The Octime application password and the support portal password are not synchronized unless the company has unified the two via SSO.
5. Force the update of the myOCTIME mobile application
Connection errors on myOCTIME frequently occur after a server update not followed by a client update. The mobile application caches outdated API settings that cause silent authentication errors.
The sequence to follow: completely uninstall the application (not just update it), restart the device, reinstall from the store, and then reconnect. On Android, also check that the application data has been cleared in Settings > Apps > myOCTIME > Storage > Clear data.
6. Check the availability of Octime servers before any local diagnosis
Before modifying anything on the workstation or network, checking if the problem comes from the Octime server itself avoids wasting time on a false diagnosis. SaaS infrastructure outages affect all users simultaneously, which is the first clue.
Asking colleagues on the same site remains the quickest test. Additionally, third-party monitoring tools can verify if the Octime domain is responding correctly. If the server is down, no local manipulation will change anything: you must wait for the resolution on the publisher’s side and check the support portal for any declared service incident.
7. Disable browser extensions that intercept authentication requests
Ad blockers, privacy extensions (uBlock Origin, Privacy Badger), and built-in VPNs in the browser regularly intercept third-party cookies necessary for the SSO flow. The result: a blank page or a redirection loop identical to that of an expired token.
We find that the most reliable test is to open a private browsing window with no active extensions, then attempt to log in. If access works in private browsing, disabling extensions one by one in normal mode helps identify the one that blocks the flow. “Anti-tracker” type extensions are the first suspects, as they specifically target the cross-domain cookies used by SSO.
Diagnosing a blocked Octime connection follows a layered logic: server first, network next, browser and client workstation last. Applying these checks in order avoids most unnecessary back-and-forth with support and allows access to be restored in just a few minutes in the vast majority of cases.