Skip to content

Incorrect Policy Type for Post Authentication Sessions (POST_AUTH_SESSION vs. CONTINUOUS_ACCESS) #508

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

Open
ozan-backupta opened this issue Mar 10, 2025 · 1 comment
Labels
bug Something isn't working stale

Comments

@ozan-backupta
Copy link

ozan-backupta commented Mar 10, 2025

Describe the bug?

The Open API specification file okta-management-APIs-oasv3-noEnums-inheritance.yaml included in the latest Okta GO SDK still references the obsolete CONTINUOUS_ACCESS keyword for Post Auth Session policies. The most recent specification defines the correct policy type as POST_AUTH_SESSION, which causes a mismatch and prevents retrieval of Post Auth Session policies using typed records.

What is expected to happen?

The SDK should use the POST_AUTH_SESSION type following the updated Open API specification to allow successful retrieval of Post Auth Session policies.

What is the actual behavior?

The Okta Go SDK uses the obsolete CONTINUOUS_ACCESS policy type for Post Authentication Session policies.

Reproduction Steps?

  • Use the latest Okta Go SDK.
  • Attempt to retrieve Post Authentication Session policies using the SDK's generated policy models. Specifically PolicyAPI.ListPolicies method with "POST_AUTH_SESSION" type.
  • Observe that the ContinuousAccessPolicy property of the returned records is empty.

Additional Information?

No response

Golang Version

go version go1.23.2 darwin/arm64

SDK Version

v5

OS version

Darwin Ozans-MacBook-Pro.local 24.3.0 Darwin Kernel Version 24.3.0: Thu Jan 2 20:23:36 PST 2025; root:xnu-11215.81.4~3/RELEASE_ARM64_T8112 arm64

@ozan-backupta ozan-backupta added the bug Something isn't working label Mar 10, 2025
Copy link

This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the stale label.

@github-actions github-actions bot added the stale label Mar 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale
Projects
None yet
Development

No branches or pull requests

1 participant