The on-demand licensing functionality introduced in 12.2 is supported by the kernel and WolframScript. It's usually activated by starting WolframScript with either the -entitlement argument or the WOLFRAMSCRIPT_ENTITLEMENTID environment variable. As the Wolfram Language Jupyter kernel interacts with the WolframKernel process directly, this environment variable is ignored. This PR detects the WOLFRAMSCRIPT_ENTITLEMENTID environment variable and passes it through to WolframKernel on the command line along with the appropriate -pwfile argument (which in WolframScript is added automatically).
I have tested these changes via configure-jupyter.wls in Linux. I have not tested on Windows or macOS, nor have I tested configuring Jupyter via the functions in the paclet instead of the script.
The on-demand licensing functionality introduced in 12.2 is supported by the kernel and WolframScript. It's usually activated by starting WolframScript with either the
-entitlementargument or theWOLFRAMSCRIPT_ENTITLEMENTIDenvironment variable. As the Wolfram Language Jupyter kernel interacts with the WolframKernel process directly, this environment variable is ignored. This PR detects theWOLFRAMSCRIPT_ENTITLEMENTIDenvironment variable and passes it through to WolframKernel on the command line along with the appropriate-pwfileargument (which in WolframScript is added automatically).I have tested these changes via
configure-jupyter.wlsin Linux. I have not tested on Windows or macOS, nor have I tested configuring Jupyter via the functions in the paclet instead of the script.