generator-office: SSO Example fails with UnhandledPromiseRejection

For anyone that wants to use .env file to store the CLIENT_SECRET and doesn’t want to fork the package or run the whole configure-sso script, I made a short script that only does the secret adding into windows credentials part using the ps1 script from the library.

require('dotenv').config();
const { execSync } = require('child_process');
const { userInfo } = require('os');

const path = 'node_modules/office-addin-sso/lib/scripts/addAppSecret.ps1';
const appName = 'YOUR_APP_NAME';
const user = userInfo().username;
const secret = process.env.CLIENT_SECRET;

execSync(
  `powershell -ExecutionPolicy Bypass -File "${path}" "${appName}" "${user}" "${secret}"`,
  { stdio: 'pipe' }
);

Just drop this script into the root of your project and anyone that will clone the project fresh can simply run it with a command like this:

"secret:add": "node ./addAppSecret.js"

@Chris2011 I created a Microsoft Learning module on this topic… I tried to be a bit more clean than the docs are on this credential store & how it works: https://docs.microsoft.com/en-us/learn/modules/office-add-ins-sso/7-exercise-outlook-sso

Jump down to the section Update project and developer workstation for the POSH (on Windows) or CLI (on macOS) options

I just found that it might be related to add-in name provided during configuration. When I provided name with spaces (as proposed on microsoft documentation) I’m getting the above problem. but when I used ‘-’ instead of spaces, then it worked. Hope that helps

This is still an issue for mac, its happening in the getSecretFromCredentialStore function:

export function getSecretFromCredentialStore(ssoAppName: string, isTest: boolean = false): string {
    try {
        switch (process.platform) {
            case "win32":
                const getSecretFromWindowsStoreCommand = `powershell -ExecutionPolicy Bypass -File "${defaults.getSecretCommandPath}" "${ssoAppName}" "${os.userInfo().username}"`;
                return execSync(getSecretFromWindowsStoreCommand, { stdio: "pipe" }).toString();
            case "darwin":
                const getSecretFromMacStoreCommand = `${isTest ? "" : "sudo"} security find-generic-password -a ${os.userInfo().username} -s ${ssoAppName} -w`;
                return execSync(getSecretFromMacStoreCommand, { stdio: "pipe" }).toString();;
            default:
                const errorMessage: string = `Platform not supported: ${process.platform}`;
                throw new Error(errorMessage);
        }
    } catch {
        return '';
    }
}

In the above code the win32 case wraps ${ssoAppName} in double quotes and in the darwin case it doesn’t. Once you add the double quotes it works as expected.

@davidchesnut

Thanks for the quick response. Your suggestions have been very helpful.

Thx @andrewconnell. It looks much cleaner and better 😃. Thx a alot.

Doing the SSO quickstart here: https://docs.microsoft.com/en-us/office/dev/add-ins/quickstarts/sso-quickstart#configure-sso

Specifically, it says:

This command (meaning npm run configure-sso) will fail if your tenant is configured to require two-factor authentication. In this scenario, you’ll need to manually complete the Azure app registration and SSO configuration steps, as described in the Create a Node.js Office Add-in that uses single sign-on tutorial.

This doesn’t tell you what to do with the secret. I was able to run configure-sso so I’m past that. Now I just need to figure out why Excel isn’t opening when I run the project 😄

I just found that it might be related to add-in name provided during configuration. When I provided name with spaces (as proposed on microsoft documentation) I’m getting the above problem. but when I used ‘-’ instead of spaces, then it worked. Hope that helps

Yeah, I followed those steps too. My ENV file contains CLIENT_ID, CLIENT_SECRET, GRAPH_URL_SEGMENT, NODE_ENV, PORT, and SCOPE, all set to the values from the AD registration. However, the manual does not mention the Credential Manager anywhere. Additionally, there is no (straightforward) way to add Web Credentials in Windows 10 apparently.