Server runs on Windows not on Mac

• I am running the latest version of Node and the tools
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed

Expected behavior

The add-in server should run on Windows and Mac.

Current behavior

The add-in server runs on Windows. The add-in server fails on Mac.

Steps to Reproduce

1. Generate an Outlook dedicated add-in with SSO.
2. Note: I can’t tell everything I did on the add-in though I’m using preview Outlook API with signatures and a call to a HTTPS server of mine.
3. Run the server with npm start on Windows 10: should work just fine.
4. Run the server on the latest Mac OS Big Sur with npm start: should not work, even in sudo.

Context

Mac

• Operating System: Mac OS Big Sur v11.0.1
• Node version: 14.15.0 & 14.15.1
• NPM version: 6.14.8

Windows

• Operating System: Windows 10 v19042.630
• Node version: 14.15.1
• NPM version: 6.14.8

Failure Logs

The terminal on Mac outputs this:

[0] > office-addin-taskpane-sso-js@0.0.0 start:server /Users/tobudim/code/w10test
[0] > office-addin-sso start manifest.xml
[0] 
[0] (node:2227) UnhandledPromiseRejectionWarning: false
[0] (Use `node --trace-warnings ...` to show where the warning was created)
[0] (node:2227) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
[0] (node:2227) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[0] npm run start:server exited with code 0

[TCourtneyOwen]

@tobudim The PR is at https://github.com/OfficeDev/Office-Addin-Scripts/pull/346. It will also require a corresponding change to to Office-Addin-SSO to add CLIENT_SECRET to the .ENV file

[TCourtneyOwen]

@tobudim The problem is that the other machines don’t have the application secret stored in the Windows Credential Manager (in the case of Windows) or the KeyChain (in the case of Mac). At the time you ran “configure-sso” an application secret is created and added the Credential Manager or KeyChain - this secret is available in the console log after running configure-sso. On your other machines, you would need to create a new entry that matches the name of your add-in project (i.e. the name you specified for your project when creating it via Yo Office) and use the application secret from the console log for this new entry. You can do this in PowerShell with the script:

$ssoAppName = ‘<add-in project name>’ $user = ‘<your user name>’ $secret = ‘<secret>.’ [void][Windows.Security.Credentials.PasswordVault, Windows.Security.Credentials, ContentType = WindowsRuntime] $creds = New-Object Windows.Security.Credentials.PasswordCredential $creds.Resource = $ssoAppName $creds.UserName = $user $creds.Password = $secret $vault = New-Object Windows.Security.Credentials.PasswordVault $vault.Add($creds)

I think we could make this a bit easier for users by adding a new “Secret” param to the .ENV file that would allow users to add the secret to this file and then the office-addin-sso package could read this value if it’s set. This would make it easier to port the project over to other machines, although having a secret hard-coded into the project is not ideal (which is why we didn’t take this approach initially).

I will work on making those changes today and can include you in the PR if you’d like.

Thanks,

Courtney