okta/okta-sdk-golang

PreviewSAMLmetadataForApplication of ApplicationSSOAPIService always return error in v4.0.0

SergiiShapoval opened this issue · 7 comments

Describe the bug?

PreviewSAMLmetadataForApplication needs both "text/xml", "application/json" Accept headers, or server will return

{"errorCode":"E0000019","errorSummary":"Bad request.  Accept and/or Content-Type headers likely do not match supported values.","errorLink":"E0000019","errorId":"<id>","errorCauses":[]}

but because of selectHeaderAccept client always set only application/json
https://github.com/okta/okta-sdk-golang/blob/v4.0.0/okta/api_application_sso.go#L127-L130

What is expected to happen?

Expect metadata retrieved correctly

What is the actual behavior?

always fail with

{"errorCode":"E0000019","errorSummary":"Bad request.  Accept and/or Content-Type headers likely do not match supported values.","errorLink":"E0000019","errorId":"oaeLG2wripTQOeBuWpGjLhhrA","errorCauses":[]}

Reproduction Steps?

create a SAML app using SDK, and then try to fetch metadata for that SAML app

Additional Information?

worked before in v2.20.0

Golang Version

1.22.0

SDK Version

v4.0.0

OS version

No response

@SergiiShapoval so this happened because the header accept need to be both "text/xml", "application/json" right? or just "text/xml" ?

@SergiiShapoval so this happened because the header accept need to be both "text/xml", "application/json" right? or just "text/xml" ?

@duytiennguyen-okta , IMO, if there will be both, it still will work

This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the stale label.

This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the stale label.

@duytiennguyen-okta , still actual

Not stale

This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the stale label.