Skip to content

Commit 64b4ac6

Browse files
committed
JFlo's first edit pass inputs + more edits + fixes from PR blockers
1 parent d8b80c7 commit 64b4ac6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/active-directory/devices/troubleshoot-mac-sso-extension-plugin.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -389,7 +389,7 @@ The following actions should take place for a successful interactive sign-on:
389389
390390
The User clicks on the **Call Microsoft Graph API** button to invoke the sign-in process.
391391

392-
:::image type="content" source="media/troubleshoot-mac-sso-extension-plugin/msal-macos-example-click-callmsftgraph.png" alt-text="Screenshot showing MSAL example app for macOS launched with Call Microsoft Graph API button.":::
392+
:::image type="content" source="media/troubleshoot-mac-sso-extension-plugin/msal-macos-example-click-call-msft-graph.png" alt-text="Screenshot showing MSAL example app for macOS launched with Call Microsoft Graph API button.":::
393393

394394
```SSOExtensionLogs
395395
//////////////////////////
@@ -543,7 +543,7 @@ Finished SSO request.
543543

544544
At this point in the authentication/authorization flow, the PRT has been bootstrapped and it should be visible in the macOS keychain access. See [Checking Keychain Access for PRT](#checking-keychain-access-for-prt). The **MSAL macOS sample** application uses the access token received from the Microsoft SSO Extension Broker to display the user's information.
545545

546-
:::image type="content" source="media/troubleshoot-mac-sso-extension-plugin/msal-macos-msft-graph-userinfo.png" alt-text="Screenshot showing the successful userinfo from the access token returned from the SSO extension Broker.":::
546+
:::image type="content" source="media/troubleshoot-mac-sso-extension-plugin/msal-macos-msft-graph-user-info.png" alt-text="Screenshot showing the successful userinfo from the access token returned from the SSO extension Broker.":::
547547

548548
Next, examine server-side [Azure AD Sign-in logs](../reports-monitoring/reference-basic-info-sign-in-logs.md#correlation-id) based on the correlation ID collected from the client-side SSO extension logs . For more information, see [Sign-in logs in Azure Active Directory](../reports-monitoring/concept-sign-ins.md).
549549

0 commit comments

Comments
 (0)