Forced re-authentication
IDE Services includes a special re-authentication mode that applies when a previously issued refresh token is invalidated according to internal organization policies. When this happens, developers must authenticate again to regain access to their IDEs.
Where re-authentication can start
Re-authentication can be initiated from two entry points:
1. Toolbox App
The developer’s only available action is to authenticate.
The UI is fully disabled — they cannot skip authentication or continue using the Toolbox App in an unauthenticated state.
No IDEs can be launched until re-authentication is completed.
2. IDE
The user can postpone re-authentication for up to 10 minutes to finish urgent tasks.
After 10 minutes, the authentication dialog appears again.
Once the developer has authenticated (either through the Toolbox App or directly in the IDE), they must click Check connection in the IDE to resume working in an authenticated state.
Enable forced re-authentication
The feature is enabled by setting the disable-blocking-authorization parameter to false in the server configuration file:
This flag defines whether developers are allowed to continue working without immediate re-authentication.
|
|
|---|---|
|
|
Emergency Use Case
If developers are unable to re-authenticate due to issues on the identity provider side, the disable-blocking-authorization flag can be temporarily switched back to true.
Set
disable-blocking-authorization: true.Restart the IDE Services Server.
When the parameter is set to true during an emergency:
The Toolbox App UI becomes unblocked.
Developers can continue using the IDE by clicking Ask again in 10 minutes in the authentication pop-up. The next pop-up they receive will be non-blocking, allowing them to keep working.