microsoftgraph / microsoftgraph/msgraph-sdk-python
missing field in authenticationstrength endpoint
還沒有人認領這個 Issue。
- 主要語言
- Python
- 星號
- 630
- 分支
- 96
- 平均合併
- 15 小時 20 分鐘
- 30 天內合併 PR
- 3
描述
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
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
從 AuthenticationStrengthPoliciesRequestBuilder 以及 policies.authentication_strength_policies.get 呼叫所使用的回應模型開始。比較 SDK 回應與 Graph Explorer 對包含 requirementsSatisfied 和 id 的 select 的回應;當 authentication strength 端點回傳 requirementsSatisfied 時即表示完成。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- python
- 領域
- api
- Issue 類型
- 缺陷
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 45/100