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 specify FEDERATION AuthenticationProvider #1562

Closed
ksj-trackunit opened this issue Sep 26, 2024 · 4 comments
Closed

Unable to specify FEDERATION AuthenticationProvider #1562

ksj-trackunit opened this issue Sep 26, 2024 · 4 comments

Comments

@ksj-trackunit
Copy link

Describe the bug?

Prior to version 18.0.0 is was possible to create a federated user like so

CreateUserRequest request = new CreateUserRequest()
        .credentials(new UserCredentials()
                .provider(new AuthenticationProvider()
                        .name("FEDERATION")
                        .type(FEDERATION)));

userApi.createUser(request, true, true, null, Map.of());

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 be OKTA even though the type is FEDERATION.

What is expected to happen?

Expected user to have FEDERATION as the provider instead of OKTA when AuthenticationProvider has type FEDERATION.

What is the actual behavior?

Specifying the type as FEDERATION will not affect the authentication provider. It will still be OKTA.

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

@arvindkrishnakumar-okta
Copy link
Contributor

@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.

@royathan
Copy link

royathan commented Oct 1, 2024

This is resolved as of 19.0.0 right?

@arvindkrishnakumar-okta
Copy link
Contributor

This bug was filed against 19.0.0

@royathan
Copy link

royathan commented Oct 1, 2024

Ah.. Turns out we were never passing that correctly :)

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

No branches or pull requests

3 participants