Skip to content

Conversation

@melissaahn
Copy link
Contributor

@melissaahn melissaahn commented Dec 23, 2025

This test has been failing again with invalid_grant; this is because the expired device code value we used is now "expired" (server side not recognizing it as a previous code anymore). So we need to update this value.

Also updating common submodule while I'm at it.

AB#3468472

Copilot AI review requested due to automatic review settings December 23, 2025 18:24
@melissaahn melissaahn requested review from a team as code owners December 23, 2025 18:24
@github-actions
Copy link

❌ Work item link check failed. Description does not contain AB#{ID}.

Click here to Learn more.

@github-actions github-actions bot added the msal label Dec 23, 2025
@github-actions github-actions bot changed the title Updating testDeviceCodeFlowTokenExpiredToken unit test Updating testDeviceCodeFlowTokenExpiredToken unit test, Fixes AB#3468472 Dec 23, 2025
@melissaahn melissaahn added the No-Changelog This change does not update the changelog. label Dec 23, 2025
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the testDeviceCodeFlowTokenExpiredToken unit test by replacing an expired device code token with a new one to ensure the test continues to function correctly.

Key Changes:

  • Updated the device code token used in the expired token test case
  • Updated the common subproject commit reference

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
msal/src/test/java/com/microsoft/identity/client/e2e/tests/mocked/DeviceCodeFlowApiTest.java Replaced expired device code token with a new token value
common Updated subproject commit reference

@p3dr0rv
Copy link
Collaborator

p3dr0rv commented Dec 23, 2025

Thanks

tokenRequest.setDeviceCode(
"BAQABIQEAAADnfolhJpSnRYB1SVj-Hgd8CWNtqmssVukUXfdCHy1XJMxy2O7R0WZgTVcQVF4A3fjnWPQ1JPXf-"
+ "SIl-NLuC9gGzGRgsLyUyknjbUReNC7vcHx8jigGiO2CkKi_Mc_YRU0E0lGH3EQZiJNwHxUc_YkTGG5DKl9sww36TdMPz-v7Bzy6cHzR6r3yQWULGNtidaogAA");
"EAQABIQEAAABlMNzVhAPUTrARzfQjWPtKRXZvU3RzQXJ0aWZhY3RzAQAAAAAAPYh9V3CvjvOB825bqyY61Bde3S6FzapbES5Yr5kuUdO4amvrqBW9JTaXBUIH9PMoK7yFKza-nSqRHL0yoxYNHhkg0f1_juE50MlJSvdXBWJEsHHZk2y2T5804dMx1QZX0739imnhE0Y9Lm1Wd5iFbaTQZrcD9oKgxxKRL8GavO4gAA");
Copy link
Contributor

Choose a reason for hiding this comment

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

EAQABIQEAAABlMNz

was this generated msal test app?

Choose a reason for hiding this comment

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

Good to include instruction or comment how to handle in case of failure, especially inputs on generating new device code? can be helpful in future,

Copy link
Contributor Author

@melissaahn melissaahn Dec 23, 2025

Choose a reason for hiding this comment

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

I'll put some instructions here: I used debug msalTestApp to run DCF with a breakpoint here, and from that breakpoint, I took the device code value. I think it took about 30 ish min to expire.

Some folks are also wondering if maybe this test isn't needed anymore. @fadidurah can you evaluate this when you get back?

Copy link
Contributor

@mohitc1 mohitc1 left a comment

Choose a reason for hiding this comment

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

:shipit:

@melissaahn melissaahn merged commit 442e312 into dev Dec 23, 2025
37 of 40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

msal No-Changelog This change does not update the changelog.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants