Skip to main content
Version: v0.3

User Settings

ORY Kratos allows users to update their own settings and profile information using two principal flows:

  • Browser-based (easy): This flow works for all applications running on top of a browser. Websites, single-page apps, Cordova/Ionic, and so on.
  • API-based (advanced): This flow works for native applications like iOS (Swift), Android (Java), Microsoft (.NET), React Native, Electron, and others.

The flow described here is implemented by the profile, password, and oidc. strategy.

Self-Service User Settings for Browser Applications

ORY Kratos supports browser applications that run on server-side (e.g. Java, NodeJS, PHP) as well as client-side (e.g. JQuery, ReactJS, AngularJS, ...).

Browser-based user settings management makes use of three core HTTP technologies:

  • HTTP Redirects
  • HTTP POST (application/json, application/x-www-urlencoded) and RESTful GET requests.
  • HTTP Cookies to prevent CSRF and Session Hijaking attack vectors.

The browser flow is the easiest and most secure to set up and integrated with. ORY Kratos takes care of all required session and CSRF cookies and ensures that all security requirements are fulfilled.

This flow is not suitable for scenarios where you use purely programmatic clients that do not work well with HTTP Cookies and HTTP Redirects.

The Settings User Interface

The Settings User Interface is a route (page / site) in your application that should render a sign in and registration form:

<!-- Profile management -->
<form action="..." method="POST">
<input type="hidden" name="csrf_token" value="cdef..." />
<input type="string" name="first_name" />
<input type="string" name="last_name" />
<input type="string" name="address" />
<input type="..." name="..." />
<input type="submit" />

<!-- Password management -->
<form action="..." method="POST">
<input type="hidden" name="csrf_token" value="cdef..." />
placeholder="Enter your new password here"

<!-- Social Sign in management -->
<form action="..." method="POST">
<input type="hidden" name="csrf_token" value="cdef..." />
<!-- ... -->

Reference these UI endpoints your ORY Kratos config file:

settings_ui: https://.../settings

In stark contrast to other Identity Systems, ORY Kratos does not render this HTML. Instead, you need to implement the HTML code in your application (e.g. NodeJS + ExpressJS, Java, PHP, ReactJS, ...), which gives you extreme flexibility and customizability in your user interface flows and designs.

Each Settings Strategy (Profile, Username and Password, Social Sign In, Passwordless, ...) works a bit different but they all boil down to the same abstract sequence:

Abstract Settings Flow


The code example used here is universal and does not use an SDK because we want you to understand the fundamentals of how this flow works.

While this example assumes a Server-Side Application, a Client-Side (e.g. ReactJS) Application would work the same, but use ORY Kratos' Public API instead.

Server-side route

You will notice that this endpoint is very similar to the one documented for User Login and Registration.

// Uses the ORY Kratos NodeJS SDK - for more SDKs check:
const { CommonApi } = require('@oryd/kratos-client');

// The browser config key is used to redirect the user. It reflects where ORY Kratos' Public API
// is accessible from. Here, we're assuming traffic going to ``
// will be forwarded to ORY Kratos' Public API.
const kratosBrowserUrl = '';

// Initializes the SDK with ORY Kratos' Admin API.
const commonApi = new CommonApi('https://ory-kratos-admin.example-org.vpc/');

// This route would be used like:
// app.get('/user/settings', authHandler('registration'))
export const settingsHandler = (req, res, next) => {
// The request ID is used to identify the login and registraion request and
// return data like the csrf_token and so on.
const request = req.query.request;
if (!request) {
console.log('No request found in URL, initializing flow.');

.then(({ body, response }) => {
if (response.statusCode !== 200) {

// "body" contains all the request data for this Registration request.
// You can process that data here, if you want.

// Lastly, you probably want to render the data using a view (e.g. Jade Template):
res.render('settings', body);
// Handle errors using ExpressJS' next functionality:
// .catch(next)


Implementing the view is simple as ORY Kratos provides you with all the information you need for rendering the forms. The following example illustrates a generic form generator (we use handlebars here) that works with ORY Kratos:

<form action="{{form.action}}" method="{{form.method}}">
{{~#each form.errors~}}
<!-- global form validation errors -->
<div class="error">{{message}}</div>

{{#each form.fields}}
{{~#each errors~}}
<!-- validation errors for this specific field -->
<div class="error">{{message}}</div>
<input name="{{name}}" type="{{type}}" value="{{value}}" {{#if disabled}}disabled{{/if}}>

<button type="submit">Save</button>

In your main "Settings" view you would then consume this template for all the methods you want to support:

<!-- Make profile changes form: -->
{{#if methods.profile.config}}
{{> form form=methods.profile.config}}

<!-- Change passowrd form: -->
{{#if methods.password.config}}
{{> form form=methods.password.config}}

<!-- ... form: -->
<!-- ... -->

For details on payloads and potential HTML snippets consult the individual Self-Service Strategies for:

Server-Side Browser Applications

Let's take a look at the concrete network topologies, calls, and payloads. Here, we're assuming that you're running a server-side browser application (written in e.g. PHP, Java, NodeJS) to render the settings screen on the server and make all API calls from that server code. The counterpart to this would be a client-side browser application (written in e.g. Vanilla JavaScript, JQuery, ReactJS, AngularJS, ...) that uses AJAX requests to fetch data. For these type of applications, read this section first and go to section Client-Side Browser Applications next.

Network Architecture

We recommend checking out the Quickstart Network Architecture for a high-level, exemplary, overview of the network. In summary:

  1. The SecureApp (your application) is exposed at and proxies requests matching path ./ory/kratos/public/* to ORY Krato's Public API Port.
  2. ORY Kratos exposes (for debugging only!!) the Public API at and Admin API at
  3. Within the "intranet" or "private network", ORY Kratos is exposed at http://kratos:4433 and http://kratos:4434. These URLs are be used by the SecureApp to communicate with ORY Kratos.

Keep in mind that his architecture is just one of many possible network architectures. It is however one of the simplest as well and it works locally. For production deployments you would probably use an Reverse Proxy such as Nginx, Kong, Envoy, ORY Oathkeeper, or others.

User Settings Process Sequence

The User Settings Flow is composed of several high-level steps summarized in this state diagram:

User Settings State Machine

  1. The flow is initiated by directing the user's browser to
  2. ORY Kratos does some internal processing (e.g. checks if a session cookie is set, generates payloads for form fields, sets CSRF token, ...) and redirects the user's browser to the Settings UI URL which is defined using the urls.settings_ui config or URLS_SETTINGS_UI environment variable, which is set to the ui endpoints - for example The user's browser is thus redirected to The request query parameter includes a unique ID which will be used to fetch contextual data for this login request.
  3. Your Server-Side Application makes a GET request to http://kratos:4434/self-service/browser/flows/requests/settings?request=abcde. ORY Kratos responds with a JSON Payload that contains data (form fields, error messages, ...) for all enabled User Profile Strategies:
    id: 'abcde',
    request_url: '...',
    methods: {
    profile: { method: 'profile', config: { action: '...', fields: [] } },
    password: { method: 'password', config: { action: '...', fields: [] } },
    oidc: { method: 'oidc', config: { action: '...', fields: [] } },
  4. Your Server-Side applications renders the data however you see fit. The User interacts with it and completes the flow by e.g. updating the password or some other profile data.
  5. The User's browser makes a request to one of ORY Kratos' Strategy URLs (e.g. or /self-service/browser/flows/settings/strategies/password?request=abcde). ORY Kratos validates the data:
    • If the form data is invalid, the Login Request's JSON Payload is updated - for example with
      id: 'abcde',
      methods: {
      oidc: {
      method: 'oidc',
      config: {
      /* ... */
      password: {
      method: 'password',
      config: {
      /* ... */
      errors: [
      message: 'The provided credentials are invalid. Check for spelling mistakes in your password or username, email address, or phone number.',
      and the user's Browser is redirected back to the Login UI:
    • If the data is valid but the modifications require proof of identity (e.g. because the primary email address or the password was changed), a login flow is executed. Only after a successful login flow will the changed data be stored!
    • If data is valid, ORY Kratos proceeds with the next step.
  6. ORY Kratos executes hooks defined in the After Settings Hooks. If a failure occurs, the whole flow is aborted.
  7. The client receives the expected response. For browsers, this is a HTTP Redirection, for API clients it will be a JSON response containing the session and/or identity. For more information on this topic check Self-Service Flow Completion.

User Settings Sequence Diagram for Server-Side Applications

Client-Side Browser Applications

Because Client-Side Browser Applications do not have access to ORY Kratos' Admin API, they must use the ORY Kratos Public API instead. The flow for a Client-Side Browser Application is almost the exact same as the one for Server-Side Applications, with the small difference that would be called via AJAX instead of making a request to https://kratos:4434/self-service/browser/flows/requests/settings?request=abcde.

To prevent brute force, guessing, session injection, and other attacks, it is required that cookies are working for this endpoint. The cookie set in the initial HTTP request made to MUST be set and available when calling this endpoint!


The initialization request ( cannot be made via AJAX or API requests. You must open that URL in the user's browser using e.g. location.href or plain and simple old <a href=...>.

Self-Service User Settings for API Clients

Will be addressed in a future release.


ORY Kratos allows you to configure hooks that run before and after a profile update was successful. For more information about hooks please read the Hook Documentation.