Skip to main content

Okta Client SDK

Design Guidelines, Evolution, and Reference Documentation for Okta's Client SDK ecosystem

Developer Experience (DX)

All primary developer scenarios should be accomplished simply with one line of code.

Composable and sensible classes that follow rational naming conventions allow you to "discover" APIs without the need for documentation, but with inline API documentation when you need it.

Security & Defaults OOTB

All features "Do The Right Thing" out of the box, with sensible defaults, security-first approaches, and default implementations of all overridable interfaces pre-assigned.

All core business logic uses interfaces to support customization or replacement without requiring the code to be forked.

Modularized Ecosystem

SDK components are modularized, allowing developers to pull in just the features they need.

SDK libraries can be extended, with higher-order abstractions or capabilities added over time.