Why?
When a user starts the Novacura client without a previous Novacura session, they authenticate with Entra ID before opening an application.

When the application is started for the first time and a REST Connector needs to acquire a token, the token request is currently performed as an interactive sign-in. This is visible as an interactive authentication request in the Entra ID sign-in logs.

At this point, the user already has a valid Entra ID session. Requiring another interactive authentication request is therefore unnecessary and prevents the initial REST call from providing a seamless single sign-on experience.

Refresh token handling for subsequent requests is already working correctly when offline_access is configured. The requested change concerns the initial token acquisition in a new Novacura session.

What?
When a REST Connector requests an authentication token for the first time in a new Novacura session, it should attempt to acquire the token silently when the user already has a valid Entra ID session.

Expected flow:

1. User starts the Novacura client without a previous Novacura session.
2. User signs in using Entra ID.
3. User starts an application for the first time.
4. The application performs a REST call requiring an Entra ID token.
5. The REST Connector acquires the token silently using the existing Entra ID session instead of initiating another interactive sign-in.

Or if the popup dialog box for the REST connector could be bypassed, this would likely work.