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

Connect-MgGraph : Invalid JWT access token #2879

Closed
WilsonAlan opened this issue Jul 30, 2024 · 6 comments
Closed

Connect-MgGraph : Invalid JWT access token #2879

WilsonAlan opened this issue Jul 30, 2024 · 6 comments
Assignees

Comments

@WilsonAlan
Copy link

Describe the bug

Unable to connect to MgGraph - Invalid JWT access token.

Expected behavior

Successful Connection.

How to reproduce

Connect-MgGraph -Scopes UserAuthenticationMethod.ReadWrite.All ( Any Scope)

SDK Version

2.20.0

Latest version known to work for scenario above?

1.12.3

Known Workarounds

Referring to bug #2569, the user vukica91 commented that reverting to version 1.12.3 worked. That worked for me as well. Other versions may also work. I did not try all versions.

Debug output

Click to expand log ```
</details>


### Configuration

$PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.22000.3079
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22000.3079
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Windows 11 X64

### Other information

That is also the case for me. That bug was closed as completed by a bot on 02/13. That is incorrect. The bug still exists. It is not resolved. I am using a work/school account, not a personal account.
@WilsonAlan WilsonAlan added status:waiting-for-triage An issue that is yet to be reviewed or assigned type:bug A broken experience labels Jul 30, 2024
@timayabi2020 timayabi2020 added Status: Needs Investigation and removed status:waiting-for-triage An issue that is yet to be reviewed or assigned labels Aug 6, 2024
@timayabi2020
Copy link
Contributor

@WilsonAlan kindly confirm if you are using a school/work or personal account.

@timayabi2020 timayabi2020 added status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close and removed Status: Needs Investigation type:bug A broken experience labels Aug 6, 2024
@WilsonAlan
Copy link
Author

WilsonAlan commented Aug 6, 2024 via email

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs: Attention 👋 and removed status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close labels Aug 6, 2024
@timayabi2020
Copy link
Contributor

@WilsonAlan I am not able to reproduce this issue. Could you kindly share the output of this command [System.AppDomain]::CurrentDomain.GetAssemblies() | Where-Object Location | Sort-Object -Property FullName | Select-Object -Property FullName, Location | Out-GridView after running Connect-MgGraph using the latest version?

@timayabi2020 timayabi2020 added status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close and removed Needs: Attention 👋 labels Aug 8, 2024
@WilsonAlan
Copy link
Author

WilsonAlan commented Aug 12, 2024 via email

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs: Attention 👋 and removed status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close labels Aug 12, 2024
@timayabi2020
Copy link
Contributor

@WilsonAlan then I highly suspect that there were conflicts in terms of capabilities between the old Azure.Core and Azure.Identity assemblies provided by 1.25.0 and the ones provided by 2.20.0/1 and also the installed Az modules. So, I'm closing this issue for now since you've confirmed that you were able to have the authentication working by deleting old modules.

@WilsonAlan
Copy link
Author

WilsonAlan commented Aug 12, 2024 via email

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

No branches or pull requests

3 participants