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

Adding ACS endpoints to an SAML app configuration in Terraform using okta_app_saml resource does not keep the order and takes only default indices. #2173

Open
jgeorge-1 opened this issue Jan 14, 2025 · 2 comments
Labels
bug triaged Triaged into internal Jira

Comments

@jgeorge-1
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

0.14.4

Affected Resource(s)

  • okta_app_saml

Terraform Configuration Files

resource "okta_app_saml" "cb_saml_example_app" {


acs_endpoints = ["https://example.com/acs1”,
"https://example.com/acs2”,
"https://example.com/acs3/“
]

}

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key: https://keybase.io/hashicorp

Debug Output

Please provide a link to a GitHub Gist containing the complete debug output. Please do NOT paste the debug output in the issue; just paste a link to the Gist.

To obtain the debug output, see the Terraform documentation on debugging.
--->
N/A

Panic Output

N/A

Expected Behavior

The ACS URLs should be in the order in which it was configured in Terraform. Also it should not just to default to
indices starting from 0,1,2 and so on.

URL -> Index
"https://example.com/acs1” -> 1
"https://example.com/acs2” -> 2
"https://example.com/acs3/“ -> 3

Can this be done in the Admin UI?

YES
Note: A subsequent Terraform apply will reset the ACS URL indices to default.

Can this be done in the actual API call?

NO
Tried the API call but it would not set the index.

Actual Behavior

The ACS URLs were out of order and starting with the default index 0,1,2 and so on...
URL -> Index
"https://example.com/acs3” -> 0
"https://example.com/acs2” -> 1
"https://example.com/acs1/“ -> 2

After saml client configuration the following step is performed.

  1. terraform apply

Important Factoids

None

References

i

No previous Github issues for this issue.
Vendor documentation:
Okta provider documentation for acs_endpoints

  • #0000
@duytiennguyen-okta duytiennguyen-okta added bug triaged Triaged into internal Jira labels Jan 14, 2025
@duytiennguyen-okta
Copy link
Contributor

OKTA internal reference https://oktainc.atlassian.net/browse/OKTA-852344

@jgeorge-1
Copy link
Author

---> Updated description
Can this be done in the actual API call?
YES
Tried the API call it sets the index only when ALL parameters (including required ones as in documentation) are included for the SAML settings in the call. It replaces rather than updating the SAML settings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug triaged Triaged into internal Jira
Projects
None yet
Development

No branches or pull requests

2 participants