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

remote saml_metadata_document #13

Closed
ghost opened this issue Nov 7, 2018 · 4 comments · Fixed by #158
Closed

remote saml_metadata_document #13

ghost opened this issue Nov 7, 2018 · 4 comments · Fixed by #158

Comments

@ghost
Copy link

ghost commented Nov 7, 2018

This issue was originally opened by @tomdavidson as hashicorp/terraform#5848. It was migrated here as a result of the provider split. The original body of the issue is below.


I would like to reference a remote document over https in creating a aws_iam_saml_provider rather than a local file, something similar to modules' source = "github.com/.... such as:

resource "aws_iam_saml_provider" "default" {
    name = "myprovider"
    saml_metadata_document = "${file("https://domain.local/idp/shibboleth")}"
}

The remote file seems especially relevant in this case - am I overlooking existing functionality?

@Sluggerman
Copy link

We have the same use case for SAML IdP. It would help to support xml document as well

@tmccombs
Copy link

It's almost possible using the http provides, were it not for this:

This URL must respond with a 200 OK response and a text/* or application/json Content-Type.

So, it fails if the response has a Content-Type like application/xml or application/samlmetadata+xml. You know, the content types typically used for saml metadata.

@sebastianmacarescu
Copy link

Any news on this one?

Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants