Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for application/samlmetadata+xml #258

Open
1 task done
cdobbyn opened this issue Mar 28, 2023 · 1 comment
Open
1 task done

Support for application/samlmetadata+xml #258

cdobbyn opened this issue Mar 28, 2023 · 1 comment

Comments

@cdobbyn
Copy link

cdobbyn commented Mar 28, 2023

Terraform CLI and Provider Versions

Terraform v1.3.9
on linux_amd64

  • provider registry.terraform.io/hashicorp/aws v4.33.0

Use Cases or Problem Statement

This is a text type, not binary data. The accept type is actually:
application/samlmetadata+xml;charset=ISO-8859-1

This simply displays a warning, and that's fine I can live with that. I imagine I'm not the only person who's confused by this not being included.

In my case I'm getting metadata from Okta and passing it into aws to provision the identity provider in there.

Proposal

My preference would be this doesn't show a warning, this return type is a valid xml document.

How much impact is this issue causing?

Low

Additional Information

This is more annoying than an issue, I've marked the impact low as a result of this.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@bendbennett
Copy link
Contributor

Hi @cdobbyn 👋

Thank you for raising this issue. It looks like application/samlmetadata+xml would be recognised as a text type by the regular expression check but that the charset for ISO-8859-1 is not present in the list of charsets that are checked.

We will consider modifying the list of charsets alongside any other updates that modify the behaviour of the checking of the Content-Type.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants