microsoftgraph / microsoftgraph/msgraph-sdk-python
missing field in authenticationstrength endpoint
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Python
- Sterne
- 630
- Forks
- 96
- Ø Merge
- 15 Std. 20 Min.
- Gemergte PRs (30 T.)
- 3
Beschreibung
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",
"combinationConfigurations@odata.context": "https://graph.microsoft.com/v1.0/$metadata#policies/authenticationStrengthPolicies('00000000-0000-0000-0000-000000000002')/combinationConfigurations",
"combinationConfigurations": []
},
{
"id": "00000000-0000-0000-0000-000000000003",
"combinationConfigurations@odata.context": "https://graph.microsoft.com/v1.0/$metadata#policies/authenticationStrengthPolicies('00000000-0000-0000-0000-000000000003')/combinationConfigurations",
"combinationConfigurations": []
},
{
"id": "00000000-0000-0000-0000-000000000004",
"combinationConfigurations@odata.context": "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",
"combinationConfigurations@odata.context": "https://graph.microsoft.com/v1.0/$metadata#policies/authenticationStrengthPolicies('00000000-0000-0000-0000-000000000002')/combinationConfigurations",
"combinationConfigurations": []
},
{
"id": "00000000-0000-0000-0000-000000000003",
"requirementsSatisfied": "mfa",
"combinationConfigurations@odata.context": "https://graph.microsoft.com/v1.0/$metadata#policies/authenticationStrengthPolicies('00000000-0000-0000-0000-000000000003')/combinationConfigurations",
"combinationConfigurations": []
},
{
"id": "00000000-0000-0000-0000-000000000004",
"requirementsSatisfied": "mfa",
"combinationConfigurations@odata.context": "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
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginnen Sie bei AuthenticationStrengthPoliciesRequestBuilder und dem Antwortmodell, das vom Aufruf policies.authentication_strength_policies.get verwendet wird. Vergleichen Sie die SDK-Antwort mit der Graph-Explorer-Antwort für ein select, das requirementsSatisfied und id enthält; die Aufgabe ist abgeschlossen, wenn requirementsSatisfied für den Authentication-Strength-Endpunkt zurückgegeben wird.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- python
- Bereich
- api
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 45/100