-
Notifications
You must be signed in to change notification settings - Fork 252
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
Calling MsGraph API using Graph SDK v5 hitting error 'A security error occurred' #2176
Comments
Thanks for raising this @kyzhangZao Any chance you can confirm the manner in which you are initialing your graph client and the dotnet runtime as well? Are you able to confirm if you are making requests being a network proxy by any chance? |
We're using .NET Framework 4.7.2 We're a MS 1p service, by any chance I can directly reach out on Teams? That might be easier to solve this issue. |
@kyzhangZao this seems to indicate the client tried to reach out Microsoft Graph through an older version of TLS and got a connection denied. Please make sure another section of your code is not locking TLS to a specific version Transport Layer Security (TLS) best practices with the .NET Framework - .NET Framework | Microsoft Learn (Microsoft Graph only supports TLS 1.2 and 1.3 for security reasons SSL Server Test: graph.microsoft.com (Powered by Qualys SSL Labs)) |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
I'm currently working on upgrade our graph sdk from v3 to v5 and graph.core sdk from v1.22 to v3. I created the GraphServiceClient with related bearer token using IAccessTokenProvider and BaseBearerTokenAuthenticationProvider. This creates the GraphServiceClient without any error, however when making MsGraph API call using that GraphServiceClient, always hitting
Error 12175 calling WINHTTP_CALLBACK_STATUS_REQUEST_ERROR, 'A security error occurred'
.The full error traces:
We're seeing this behavior when running integration test. And based on our investigation, when using the new graph sdk, MsGraph mock (using mountebank) is not being triggered, instead, the call seems to try to reach the localhost endpoint that gives this error. This issue only being found when trying to call MsGraph API, other calls reach mountebank.
The text was updated successfully, but these errors were encountered: