[AndrewCraswell]

Purpose

Currently we only expose the Account info when authentication completes. This is not sufficient because, for example, this would not give access to the state data which is needed for many security scenarios. The full authentication details are exposed by msal using the AuthResponse, and we should be returning this data and storing in Redux.

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Documentation content changes
[ ] Other... Please describe:

How to Test

• Get the code
• Run the sample app and verify the AuthResponse is saved in the Redux store as authenticationResponse using the React DevTools extension.

[AndrewCraswell]

My team hit a blocker where we need to be able to access some of the data in the AuthResponse in order to implement a feature. I hadn't realized that we weren't exposing that after authentication, so this PR remedies that. It also actually simplifies the code a bit.

We have a demo with our CVP early next week so I was hoping to get this in by the weekend if at all possible.

[AndrewCraswell]

All of the token data and account info already exists in the AuthResponse object, but I've elected to keep the previous values to prevent breaking changes.

[omusavi]