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

Unable to add attribute statements to SAML application #731

Open
kingofzeal opened this issue Jul 25, 2024 · 3 comments
Open

Unable to add attribute statements to SAML application #731

kingofzeal opened this issue Jul 25, 2024 · 3 comments
Labels

Comments

@kingofzeal
Copy link

kingofzeal commented Jul 25, 2024

Describe the bug?

Observed when trying to update a SamlApplication to add attribute statements. The request is responded to as if it was successful, however the response indicates no change to the application.

What is expected to happen?

The app is updated to include the attribute specified by the request.

What is the actual behavior?

The request response indicates a 200 OK, but the response payload does not have the updated attributes.

Reproduction Steps?

  • Obtain a SAML application using the ApplicationApi
  • Modify the context of app.Settings.SignOn.AttributeStatements.AttributeStatement in some way - add a new value, or modify an existing entry in the list.
  • Save the app using ApplicationApi.ReplaceApplicationAsync(app.Id, app)

Additional Information?

After making a known good request, comparing it with the request from the SDK (captured via Fiddler) and using Postman to manually adjust the request payloads, it appears that including the property destinationOverride in the request (even if set to null) is required for the attribute statement to be added/updated as expected.

.NET Version

8.0.300

SDK Version

7.0.6 and 8.0.1

OS version

No response

@kingofzeal kingofzeal added the bug label Jul 25, 2024
@bryanapellanes-okta
Copy link
Contributor

@kingofzeal Thanks for reporting this. I've entered an internal issue for tracking and prioritization. OKTA-754285

@bryanapellanes-okta
Copy link
Contributor

OKTA-807224

@bryanapellanes-okta
Copy link
Contributor

@kingofzeal Quick update on this. The issue appears to be with the server side API and not the SDK. A ticket to address the issue is in the backlog to be addressed by the owning team. OKTA-807224

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

No branches or pull requests

2 participants