-
Notifications
You must be signed in to change notification settings - Fork 84
Open
Labels
status:waiting-for-triageAn issue that is yet to be reviewed or assignedAn issue that is yet to be reviewed or assignedtype:bugA broken experienceA broken experience
Description
Describe the bug
When I use the SDK, I don't get the requirementsSatisfied field, but when I call it though graph explorer I do get the field.
I am calling the endpoint like so:
query_params = AuthenticationStrengthPoliciesRequestBuilder.AuthenticationStrengthPoliciesRequestBuilderGetQueryParameters(
select=["requirementsSatisfied", "id"]
)
config = BaseRequestConfiguration(query_parameters=query_params)
result = await self.client.policies.authentication_strength_policies.get(
request_configuration=config
)
And I am getting this response:
{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#policies/authenticationStrengthPolicies(requirementsSatisfied,id)",
"value": [
{
"id": "00000000-0000-0000-0000-000000000002",
"[email protected]": "https://graph.microsoft.com/v1.0/$metadata#policies/authenticationStrengthPolicies('00000000-0000-0000-0000-000000000002')/combinationConfigurations",
"combinationConfigurations": []
},
{
"id": "00000000-0000-0000-0000-000000000003",
"[email protected]": "https://graph.microsoft.com/v1.0/$metadata#policies/authenticationStrengthPolicies('00000000-0000-0000-0000-000000000003')/combinationConfigurations",
"combinationConfigurations": []
},
{
"id": "00000000-0000-0000-0000-000000000004",
"[email protected]": "https://graph.microsoft.com/v1.0/$metadata#policies/authenticationStrengthPolicies('00000000-0000-0000-0000-000000000004')/combinationConfigurations",
"combinationConfigurations": []
}
]
}
So the RequirementsSatisfied field is missing. However, when I call the same endpoint with the same parameters in the graph explorer, I do get the right response:
{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#policies/authenticationStrengthPolicies(requirementsSatisfied,id)",
"value": [
{
"id": "00000000-0000-0000-0000-000000000002",
"requirementsSatisfied": "mfa",
"[email protected]": "https://graph.microsoft.com/v1.0/$metadata#policies/authenticationStrengthPolicies('00000000-0000-0000-0000-000000000002')/combinationConfigurations",
"combinationConfigurations": []
},
{
"id": "00000000-0000-0000-0000-000000000003",
"requirementsSatisfied": "mfa",
"[email protected]": "https://graph.microsoft.com/v1.0/$metadata#policies/authenticationStrengthPolicies('00000000-0000-0000-0000-000000000003')/combinationConfigurations",
"combinationConfigurations": []
},
{
"id": "00000000-0000-0000-0000-000000000004",
"requirementsSatisfied": "mfa",
"[email protected]": "https://graph.microsoft.com/v1.0/$metadata#policies/authenticationStrengthPolicies('00000000-0000-0000-0000-000000000004')/combinationConfigurations",
"combinationConfigurations": []
}
]
}
Expected behavior
I expect the SDK to return the same response that is returned in graph explorer.
How to reproduce
Call the Authentication strength endpoint.
SDK Version
latest
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
Configuration
No response
Other information
No response
Metadata
Metadata
Assignees
Labels
status:waiting-for-triageAn issue that is yet to be reviewed or assignedAn issue that is yet to be reviewed or assignedtype:bugA broken experienceA broken experience