Overview

Integrates a Kit app with the NVIDIA License Service (NLS).

The system administrator will need to obtain an API key and client configuration token from their NLS instance.

Both must be placed in each user’s .nvidia-omniverse/config/nls directory; the API key in a file called api_key and the client configuration token as a client_config.tok file.

If desired, these files can be placed in a different directory, which must then be specified using the NLS_CONFIGURATION_PATH environment variable.

Licence compliance can be enforced by setting the NLS_ENFORCE_COMPLIANCE environment variable to a non-zero value, or the /exts/omni.kit.nls/enforceCompliance setting to true.

SSL certificate verification

NLS HTTPS connections are controlled by the /exts/omni.kit.nls/verify_cert setting. The default value is false for compatibility with existing enterprise NLS deployments that may not have certificates trusted by the local system.

When /exts/omni.kit.nls/verify_cert is false, SSL hostname verification and certificate verification are disabled. The extension logs a startup warning in this configuration so administrators can see when NLS traffic is not certificate-verified. Set /exts/omni.kit.nls/verify_cert to true after configuring a valid certificate for the NLS server. To keep the compatibility behavior but suppress the startup warning, set /exts/omni.kit.nls/warn_on_verify_cert_disabled to false.