-
Notifications
You must be signed in to change notification settings - Fork 135
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 specify FEDERATION AuthenticationProvider #1562
Labels
Comments
@ksj-trackunit Thanks for posting! This looks like a bug introduced with our recent Open API Spec update. I'll get the spec fixed and SDK released soon. |
This is resolved as of 19.0.0 right? |
This bug was filed against 19.0.0 |
Ah.. Turns out we were never passing that correctly :) |
13 tasks
arvindkrishnakumar-okta
added a commit
that referenced
this issue
Jan 27, 2025
arvindkrishnakumar-okta
added a commit
that referenced
this issue
Jan 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug?
Prior to version 18.0.0 is was possible to create a federated user like so
After upgrading to the latest version the
.name()
field is made private and it is no longer possible to set it. When omitting the field the provider will beOKTA
even though the type isFEDERATION
.What is expected to happen?
Expected user to have
FEDERATION
as the provider instead ofOKTA
whenAuthenticationProvider
has typeFEDERATION
.What is the actual behavior?
Specifying the type as
FEDERATION
will not affect the authentication provider. It will still beOKTA
.Reproduction Steps?
Create a user via SDK using the snippet provided in the bug report using SDK version 18+.
Additional Information?
No response
Java Version
openjdk 21 2023-09-19
OpenJDK Runtime Environment (build 21+35-2513)
OpenJDK 64-Bit Server VM (build 21+35-2513, mixed mode, sharing)
SDK Version
18.0.0 and 19.0.0
OS version
No response
The text was updated successfully, but these errors were encountered: