search

okta / okta-sdk-dotnet

A .NET SDK for interacting with the Okta management API, enabling server-side code to manage Okta users, groups, applications, and more.
Other
160 stars 100 forks source link

AuthorizationServerPolicy no longer derives from Policy in v9.0.0 #749

Closed Stef-Vi closed 2 weeks ago

Stef-Vi commented 1 month ago

Describe the bug?

We've noticed that the AuthorizationServerPolicy type no longer derives from the Policy type when upgrading to v9.0.0. This is not mentioned in the SDK migration guide. When upgrading to v9.0.0, it is no longer possible to set and read the policy properties when using this type. What is the recommended migration approach here? Is this change by design, and if so, are we expected to use the PolicyApi to get more information and edit properties?

What is expected to happen?

When using the newly created APIs to edit the authorization server policy we expected to still have the option to read and write properties like 'name', 'description', 'priority'.

What is the actual behavior?

The new API calls uses the model AuthorizationServerPolicy without inheriting Policy. This causes the properties to not be set.

Reproduction Steps?

Upgrade the package to v9.0.0 and try to fetch an existing authorization server policy or create a new authorization server policy. You will notice that the properties only known in the Policy models are missing. It is not possible to set these properties anymore.

Additional Information?

No response

.NET Version

.NET 8.0.0

SDK Version

v9.0.0

OS version

No response

bryanapellanes-okta commented 1 month ago

@Stef-Vi Thanks for your inquiry. I have opened an internal issue for tracking and prioritization. OKTA-821864

We will consult with the internal team that owns this area of the API and request further guidance be provided here.