vurcircle.blogg.se - Salesforce platform app builder register webacess

The Office host application returns the access token to the add-in as part of the result object returned by the getAccessToken call.

Office will cache the token on your behalf so that future calls to getAccessToken simply return the cached token.

The Microsoft identity platform returns the access token to Office.

The Office host application requests the access token from the Microsoft identity platform for the current user.

If this is the first time the current user has used your add-in, they are prompted to consent.

Office redirects to the Microsoft identity platform to complete the sign-in process.

If the user is not signed in, the Office host application opens a dialog box for the user to sign in.

If the user is already signed in to Office, the Office host will return the access token with the claims of the signed in user.

In the add-in, your JavaScript code calls the Office.js API getAccessToken.

The gray elements represent the code you write and include the client-side code (task pane) and the server-side code for your add-in. The blue elements represent Office or the Microsoft identity platform. The following diagram shows how the SSO process works. Take advantage of this and use single sign-on (SSO) to authenticate and authorize the user to your add-in without requiring them to sign in a second time. Users sign in to Office using either their personal Microsoft account or their Microsoft 365 Education or work account.