Authentication support in SDK about okta-sdk-java HOT 8 CLOSED

@RvPr The AuthN API would be the way to go. We are planning on adding this functionality, but it will likely not happen within the month. Please contact [email protected] with any questions about migration, we can help suggest alternatives.

from okta-sdk-java.

Has this ever been implemented? I am looking at upgrading from version 0.0.4 of the Okta sdk, but this is a feature we would need.

from okta-sdk-java.

Fwiw, I'm using the current latest version of the SDK (0.0.6) and the AuthenticateUser API is not implemented in it. I've defaulted to using Primary Authentication with Trusted Application for the authentication part, and using the SDK for User and Group CRUD.

from okta-sdk-java.

Hi!

We're trying to reduce the number of calls we're making to okta cause we sometimes get rate-limited. We wanted to use the built in caching mechanism but it lost some of it's value for us because the authentication using access-token and refresh-token is not built in to the SDK. Is this something you plan on implementing or maybe there's another approach/best practice to limit the number of calls we make for authenticating users using access tokens?

Sorry for hi-jacking the thread but it's related to the authentication and maybe it can help other people too.

Thank you,
Joel

from okta-sdk-java.

We are keeping the SDK and the authentication/authorization projects decoupled when possible.

Take a look at these projects:

• okta/okta-jwt-verifier-java - generic Java ID and access token handling
• okta/okta-spring-security - Okta client side access token handling

Though in the near future we will also allow access to the SDK from integrations like Spring, in order to do things like go from the current logged in Principal to an Okta SDK 'User' class (like we did with Stormpath's integrations)

from okta-sdk-java.

@bdemers Does this mean the AuthN api will not be supported in the Okta SDK? Neither repo you linked seems to handle that.

from okta-sdk-java.

@me717 we will be working on that. Not sure which repo it will fit into yet.
A lot of AuthN use cases can be handled by OAuth/OIDC flows (transparent to the developer/user). There are a few things that cannot be like the Sessions API.

Which AuthN API calls are you using today? (this will help us prioritize the order we work on them)

from okta-sdk-java.

AuthN support will likely NOT go in this repo. If we support it will likely be a separate project. I'd highly recommend looking at OAuth/OIDC flows as a replacement.

from okta-sdk-java.