Okta Authentication SDK + Servlet
27 | 28 |Hello!
31 |If you're viewing this page then you have successfully configured and started this example server.
32 |This example shows you how to use the Okta 33 | Authentication SDK configured for a basic Servlet application.
34 | 35 |Is This Library Right for Me?
37 |38 | The Authentication SDK is a convenient HTTP client wrapper for Okta's Authentication API. These APIs are powerful and useful if you need to achieve one of these cases: 39 |
40 |-
41 |
- You have an existing application that needs to accept primary credentials (username and password) and do custom logic before communicating with Okta. 42 |
- You have significantly custom authentication workflow or UI needs, such that Okta's hosted sign-in page or Sign-In Widget do not give you enough flexibility. 43 |
46 | The power of this SDK comes with more responsibility and maintenance: you will have to design your authentication workflow and UIs by hand, respond to all relevant states in Okta's authentication state machine, and keep up to date with new features and states in Okta. 47 |
48 |49 | Otherwise, most applications can use the Okta hosted sign-in page or the Sign-in Widget. For these cases, you should use Okta's Spring Boot Starter or other OIDC/OAuth 2.0 library. 50 |
51 |