microsoftgraph / microsoftgraph/msgraph-sdk-python
missing field in authenticationstrength endpoint
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Python
- Estrellas
- 630
- Forks
- 96
- Merge medio
- 15 h 20 min
- PR fusionados (30 d)
- 3
Descripción
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
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comienza en AuthenticationStrengthPoliciesRequestBuilder y en el modelo de respuesta utilizado por la llamada policies.authentication_strength_policies.get. Compara la respuesta del SDK con la respuesta de Graph Explorer para un select que contenga requirementsSatisfied e id; se considera terminado cuando requirementsSatisfied se devuelve para el endpoint de authentication strength.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- python
- Área
- api
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 45/100