Application v1.0 and beta APIs broken field: oauth2RequiredPostResponse
#273
Labels
Area: GraphService
An issue with the Microsoft Graph Service API
Comments
manicminer
added a commit
to hashicorp/terraform-provider-azuread
that referenced
this issue
Feb 17, 2023
This was referenced Feb 17, 2023
Merged
irvinesunday
added
the
Area: GraphService
manicminer
added a commit
to hashicorp/pandora
that referenced
this issue
Aug 12, 2024
…tResponse` field in `Application` model See: microsoftgraph/msgraph-metadata#273
manicminer
added a commit
to hashicorp/pandora
that referenced
this issue
Aug 12, 2024
…tResponse` field in `Application` model See: microsoftgraph/msgraph-metadata#273
manicminer
added a commit
to hashicorp/pandora
that referenced
this issue
Aug 12, 2024
…`Application` model in beta API See: microsoftgraph/msgraph-metadata#273
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Both the v1.0 and beta APIs have broken handling of the
oauth2RequiredPostResponsefield, in different ways:Beta API
Less urgent, the beta API seems to have this field misnamed as
oauth2RequirePostResponse- note the missingdofRequire(d). If you send a field with the documented name ofoauth2RequiredPostResponse, you get a 404 error both forPOSTandPATCHrequests, however it works with the misspelled field name.Correct name yields 404
POST /beta/applications
PATCH /beta/applications/{id}
Incorrect name is successful
POST /beta/applications
PATCH /beta/applications/{id}
v1.0 API
More urgently, the v1.0 API doesn't seem to accept either of these namings of this field and it is impossible to create an application whilst specifying this field, or to set this field on an existing application. This means we cannot currently use the v1.0 API for applications.
Correct name fails
POST /v1.0/applications
PATCH /v1.0/applications/{id}
Incorrect name also fails
POST /v1.0/applications
PATCH /v1.0/applications/{id}
The text was updated successfully, but these errors were encountered: