Ionize Docs
Get Started

Access URLs and credentials

Where to log in, and with what

After running ionctl deploy (or podman compose up -d from platform/dev), Ionize exposes the following on localhost:

Web UIs

URLWhatAuth
http://localhost:2000Site, brochure, OAuth2 playground, docsnone
http://localhost:3000Auth CIAM, customer login UIas customer
http://localhost:3001Dashboard CIAM, customer admin dashboardas admin (see below)
http://localhost:4000Auth IAM, employee login UIas employee
http://localhost:4001Dashboard IAM, employee admin dashboardas admin (see below)
http://localhost:5433pgAdmin, database administrationSSO via IAM
http://localhost:5434MailSlurper, captured emailnone

APIs

PortServicePublic/Admin
:3100CIAM Kratospublic, self-service flows
:3101CIAM Kratosadmin, identity CRUD
:3102CIAM Hydrapublic, token, discovery, JWKS
:3103CIAM Hydraadmin, client management, consent
:4100IAM Kratospublic
:4101IAM Kratosadmin
:4102IAM Hydrapublic
:4103IAM Hydraadmin
:5432PostgreSQLfive databases

In production, only ports 80 and 443 should be public. See Operate, Network Topology for the host firewall ruleset.

Default credentials (development only)

IAM Admin, used to log into Dashboard CIAM and Dashboard IAM:

FieldValue
Emailadmin@demo.user
Passwordadmin123!
Role (in traits.role)admin

pgAdmin, does not have a separate password. Click "Login with Ionize" on the pgAdmin login page and authenticate as the IAM admin above. Your database role is mapped from your OIDC role claim, see Security, pgAdmin DBA Accounts.

MailSlurper, no authentication. Outbound emails (verification links, recovery codes, notifications) are captured here; nothing is delivered to the real internet in dev.

Logging into Dashboard

The dev IAM admin credentials are seeded by iam-seed-dev.sh at first start. To log in:

  1. Open http://localhost:4001.
  2. Click "Sign in with Ionize IAM."
  3. Authenticate as admin@demo.user / admin123!.
  4. Consent to the Dashboard IAM scopes.
  5. You land on the Dashboard dashboard.

The same flow works against http://localhost:3001 (Dashboard CIAM), note that even though Dashboard CIAM is a customer-facing dashboard surface, it is operated by employees, so it authenticates via the IAM domain. The "C" in "Dashboard CIAM" describes the data the dashboard manages, not the audience using it.

Changing the default password

Before exposing any dev stack to even a coworker on your LAN, change admin@demo.user's password through the Kratos settings flow (/self-service/settings/browser) or delete the seed identity and create your own through the Dashboard UI.

In production, the seed script does not run, production admins are created through Deploy's Accounts wizard step.

On this page