Beginning in October, Okta release version notations are changing from year.month to year.week. For example, 2026.10.0 will become 2026.41.0, where 41 indicates that week of the year that the deployment occurs. More information is available in this knowledge base article.

    On this page

    Journeys

    Journeys break down your development project into consumable steps:

    • Learn the key concepts.
    • Plan for the tasks that you need to complete.
    • Build your project using how-to guides.
    • Review content related to your project, but not required to finish the project.

    Build a requesting app

    Enable Cross App Access (XAA) for your client (requesting app). Signed-in users can access data in external apps with no static keys or redundant sign-in prompts.

    Build a resource app

    Enable Cross App Access (XAA) for your resource app. Authorize external apps to call your API for authenticated users with no static keys or redundant sign-in prompts.


    Secure your first web app

    Seamlessly connect your customer-facing app to Okta and configure a secure sign-in experience, using the built-in app sign-in policies and the Okta hosted sign-in page.

    Sign users in through your web app

    Integrate Okta with your customer portal to manage user authentication (sign-in and sign-out) directly through its web interface.

    Apply your brand to the Okta user experience

    Design and apply a custom look and feel to the Okta-hosted Sign-In Widget that matches your brand.


    Add a sign-in form to your mobile app

    Use the Okta Client SDK to build a secure and complete sign-in experience for your mobile app, giving your users seamless access while protecting their data.

    Add a sign-up form to your web app

    Implement a sign-up form for your web app, reducing onboarding friction and accelerating user acquisition.

    Migrate your non-Okta user accounts to Universal Directory

    Provide a smooth and secure activation experience as you move human user identities into Universal Directory from another user store.


    Prepare to upgrade to Okta Identity Engine

    Plan, update, test, and validate your setup so that you can confidently complete a smooth Production upgrade.

    Replace Classic Engine auth flows with Identity Engine

    Replace Classic Engine authentication patterns after the Identity Engine upgrade by choosing a supported deployment model and configuring policies.

    Edit This Page On GitHub