GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — missing field in authenticationstrength endpoint · Issue #1167 · microsoftgraph/msgraph-sdk-python

missing field in authenticationstrength endpoint #1167

New issue
Copy link
New issue
Copy link
Open
Open
missing field in authenticationstrength endpoint#1167
Copy link
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

@NachoCh33s3
Ignacio Acosta (NachoCh33s3)
opened on Apr 2, 2025
Issue body actions

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

Activity

  1. Ignacio Acosta (NachoCh33s3)
    added
    status:waiting-for-triageAn issue that is yet to be reviewed or assignedAn issue that is yet to be reviewed or assigned
    type:bugA broken experienceA broken experience
    on Apr 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.