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

Error Updating OAuth Application: Missing frontchannel_logout_uri When participate_slo is True #2162

Open
avinashduthaluri opened this issue Dec 11, 2024 · 4 comments
Labels
api-parity Update resource to match current API

Comments

@avinashduthaluri
Copy link

avinashduthaluri commented Dec 11, 2024

Description:

We encountered an issue while using the Terraform Okta Plugin to update an OAuth application. The error occurs because frontchannel_logout_uri is missing when participate_slo is set to true.

Error Message:

Error: failed to update OAuth application: the API returned an error: Api validation failed: frontchannel_logout_uri. Causes: errorSummary: frontchannel_logout_uri: ''frontchannel_logout_uri'' is required when ''participate_slo'' is true.

Steps to Reproduce:

  1. Set up an OAuth application in Okta using UI.
  2. Configure frontchannel_logout_uri in the Terraform File.
  3. Attempt to apply the Terraform configuration. We get an error:
    An argument named "frontchannel_logout_uri" is not expected here.

Expected Behavior:

The application should update successfully without requiring frontchannel_logout_uri unless specifically needed.

Actual Behavior:

The update fails with an API validation error, indicating that frontchannel_logout_uri is required when participate_slo is true.

Environment:

Terraform Enterprise Version: 1.9.5
Okta Plugin Version:4.11

@fuzztooth
Copy link

Can confirm this still happens in 4.12. No idea why this would error out on a property that isn't actually available yet in the spec.

@avinashduthaluri
Copy link
Author

We tried it in 4.11 , we will retest in 4.12 and get back .

@duytiennguyen-okta duytiennguyen-okta added the api-parity Update resource to match current API label Jan 7, 2025
@avinashduthaluri
Copy link
Author

We tried in 4.11 and still the same issue.

@avinashduthaluri
Copy link
Author

Can someone please help?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api-parity Update resource to match current API
Projects
None yet
Development

No branches or pull requests

3 participants