microsoftgraph / microsoftgraph/msgraph-metadata
GET request returns 201 Created instead of 200 OK for `identity/conditionalAccess/authenticationContextClassReferences/{id}`
Nobody has claimed this yet.
- Dominant language
- XSLT
- Stars
- 166
- Forks
- 55
- Avg merge
- 16h 12m
- Merged PRs (30d)
- 14
Description
When performing a GET request on a newly created authenticationContextClassReference, the API returns a 201 Created status code. According to HTTP standards and OData conventions, a GET request should return 200 OK.
Reproduction Steps
- Create an authenticationContextClassReference (e.g., via PATCH or POST).
- Perform a GET request on the created resource URL: https://graph.microsoft.com/v1.0/identity/conditionalAccess/authenticationContextClassReferences/{id}.
Expected Behavior
Status code 200 OK.
Actual Behavior
Status code 201 Created.
Impact
Client libraries (like the Terraform provider) that expect standard HTTP status codes fail to read the resource, interpreting 201 as an unexpected response for a read operation.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the GET request against the authenticationContextClassReferences/{id} endpoint after creating a resource via PATCH or POST. Confirm the response currently returns 201 Created and verify that the completed fix returns 200 OK so client libraries such as Terraform can read the resource successfully.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100