microsoftgraph / microsoftgraph/msgraph-sdk-python

missing field in authenticationstrength endpoint

未关闭
#1,167 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

status:waiting-for-triage type:bug
主要语言
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

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 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

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。