Skip to content
Trimble Identity

Frequently Asked Questions

  1. Does this SDK library support .NET Framework?
  2. Does the SDK support token refresh?
  3. Can I customize the browser experience?
  4. How does persistent storage work in this SDK?
  5. Does the SDK support offline scenarios?

Does this SDK library support .NET Framework?

Yes! The Trimble.ID.Desktop SDK targets .NET Standard 2.0, which according to Microsoft’s .NET Standard compatibility specification is compatible with:

  • .NET Framework 4.6.1 and later versions
  • .NET Core 2.0 and later versions
  • .NET 5, 6, 7, 8 and later versions

Note: The minimum .NET Framework version (4.6.1) is determined by the .NET Standard 2.0 specification. You can verify this compatibility in Microsoft’s official .NET Standard documentation.

This ensures broad compatibility across different .NET implementations and platforms.

Does the SDK support token refresh?

Yes, the SDK includes automatic token refresh capabilities through the TokenProvider interface, ensuring your application maintains valid authentication tokens without user intervention.

Can I customize the browser experience?

Yes, the SDK provides BrowserPreferences to customize the browser launching behavior:

  • Option to open in a new window
  • Platform-specific browser handling
  • Fallback mechanisms for different environments

How does persistent storage work in this SDK?

The SDK uses Isolated Storage mechanism for storing tokens with the following features:

  • Encrypted storage - tokens are encrypted using the provided salt and secure
  • Application-specific - storage is only accessible by your application
  • Not shared between applications
  • Automatic token refresh - token lifetime and refresh are handled automatically
  • Silent login - subsequent application launches trigger automatic silent login with stored tokens

Does the SDK support offline scenarios?

Yes, the SDK supports offline access mode that allows you to:

  • Fetch user information and access tokens even when offline
  • Continue to issue new tokens when network becomes available
  • Bypass token expiration checks for existing tokens from cache
  • Retrieve information from persistent storage without active network connection

Requirements:

  • At least one successful initial sign-in to initialize the token cache
  • Must be configured with persistent storage (as shown above)
  • Offline access must be explicitly enabled
byte[] Salt = { 0xb7, 0xa2, 0x46, 0x53, 0x84, 0xf0, 0x49, 0xc6, 0x4f, 0x9b };
IAuthenticator authenticator = new LocalhostAuthenticator(endpointProvider, CLIENT_ID, SCOPES)
    .WithPersistentStorage(new EncryptedStorage(new IsolatedFileStorage("filename.config"), Salt))
    .WithOfflineAccess();