Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[identity] Fix MSAL Flow additionallyAllowedTenantIds to pass through #23704

Merged
merged 1 commit into from
Nov 4, 2022

Conversation

mpodwysocki
Copy link
Member

Packages impacted by this PR

  • [identity]

Issues associated with this PR

Describe the problem that is addressed by this PR

The additionallyAllowedTenantIds was not passed through to the base MsalFlow class to allow it to resolve the additionally allowed tenant IDs in the getToken() method. This fixes this bug and also fixes some minor ESLint issues.

What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?

Are there test cases added in this PR? (If not, why?)

Provide a list of related PRs (if any)

Command used to generate this PR:**(Applicable only to SDK release request PRs)

Checklists

  • Added impacted package name to the issue description
  • Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
  • Added a changelog (if necessary)

@azure-sdk
Copy link
Collaborator

API change check

API changes are not detected in this pull request.

@mpodwysocki mpodwysocki enabled auto-merge (squash) November 3, 2022 22:15
@@ -29,7 +29,7 @@ describe("OnBehalfOfCredential", function () {
userAssertionToken: "user-assertion",
});

const newMSALClientLogs = () =>
const newMSALClientLogs = (): number =>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is just for clarity right? was it causing some issue? curious to know @mpodwysocki

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe a lint thing, it's common to enforce explicitly declaring return types to avoid accidentally returning the wrong thing

Copy link
Member

@xirzec xirzec left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice fix!

@@ -29,7 +29,7 @@ describe("OnBehalfOfCredential", function () {
userAssertionToken: "user-assertion",
});

const newMSALClientLogs = () =>
const newMSALClientLogs = (): number =>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe a lint thing, it's common to enforce explicitly declaring return types to avoid accidentally returning the wrong thing

@mpodwysocki mpodwysocki merged commit 5a6c70c into main Nov 4, 2022
@mpodwysocki mpodwysocki deleted the bug/23693 branch November 4, 2022 22:51
@KarishmaGhiya
Copy link
Member

We'll need the same changes for msalBrowserCommon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants