dataverse-auth-clientcred

Cross-platform pure NodeJS On-behalf-of and client credential authenticaiton against Microsoft dataverse Pro. Stores the token for use with NodeJS applications such as dataverseify. This is forked from dataverse-auth

Usage

~$ npx dataverse-auth [environment]
E.g.
~$ npx dataverse-auth contosoorg.crm.dynamics.com
~$ npx dataverse-auth contosoorg.crm.dynamics.com aadappid aadappsecret

Optional - specify tenant url

You you want to specify the tenant Url rather that it be looked up automatically ~$ npx dataverse-auth [tennant] [environment]
E.g.
~$ npx dataverse-auth contoso.onmicrosoft.com contosoorg.crm.dynamics.com
~$ npx dataverse-auth contoso.onmicrosoft.com contosoorg.crm.dynamics.com aadappid aadappsecret
For more information see the dataverse-ify project

Tested on

• Linux
  • ✔ Manjaro
  • ✔ Ubuntu
  • ✔ Debian (see workaround below)
• MacOS
  • ✔ 10.15
• Windows
  • ✔ 10

Debian install

By default the Debian kernel is hardened and proactively deny unprivileged user namespaces. This causes an issue when you install electron or packages depending on it, and there are (at least) two ways to bypass that.

Method1, enable unprivileged namespaces

For NPX to work you will have to enable unprivileged user namespaces. Instructions on how to do this is found in the this article

Method2, install and modify permissions

First, install the NPM package, globally or in a dedicated project. After the install navigate to $NPM_PACKAGES/lib/node_modules/dataverse-auth/node_modules/electron/dist (tip: if you try to run dataverse-auth the full path will be in the error message) Change the owner of chrome-sandbox to root and chmod it to 4755:
~$ sudo chown root chrome-sandbox && sudo chmod 4755 chrome-sandbox

Now you can run it like any other package:
~$ dataverse-auth myorg.crm.dynamics.com