IDE Services 2026.1 Help

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.

  • To pass a login made in the IDE license activation dialog to the Toolbox App, refer to Share the IDE login with the Toolbox App.

Enable forced re-authentication

By default, developers are allowed to continue working without immediate re-authentication. Forced re-authentication interrupts developers’ work by requiring them to log in again. It can be enabled in two steps:

Step 1. Edit the server configuration file

  • Set the disable-blocking-authorization parameter to false in the server configuration file:

    tbe: unauthorized-config: disable-blocking-authorization: false

Step 2. Edit the profile setting

This step lets you enable forced re-authentication for specific profiles.

  1. In the Web UI, navigate to Profiles and select the profile for which you want forced re-authentication enabled.

  2. In the IDE Provisioner tab, select Settings + | Toolbox settings.

  3. In the Configure Toolbox Settings dialog, enable the option Block TBA and IDE usage when re-login is required.

  4. Click Save.

Forced re-login disabled (default)

Forced re-login enabled

  • Developers with an expired or invalid token can continue using the IDE.

  • The Toolbox App remains accessible (not blocked).

  • The IDE shows a non-interrupting notification prompting users to re-authenticate.

  • Developers are forced to re-authenticate as described above (through the Toolbox App or IDE).

  • The blocking mode is enabled: users cannot proceed without authenticating.

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.

  1. Set disable-blocking-authorization: true.

  2. 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.

16 November 2026