Get started
First login
Sign in with the seeded admin and orient yourself in the console.
Goal
Access the admin console and confirm you are in the right tenant.
Prerequisites
- API and Web running (Local install or Docker Compose).
- Seed enabled on the API.
Default seed credentials (development)
When Seed:Enabled=true (see src/ShieldGate.Api/appsettings.json):
| Field | Typical value |
|---|---|
| Tenant slug | platform |
admin@shieldgate.local |
|
| Password | ChangeMe!123 |
Change these immediately on any shared or production-like environment.
Steps
- Open the admin UI (
https://localhost:7280locally). - Enter tenant slug, email, and password.
- After login, open the Dashboard. You should see navigation groups such as Topology, Security, Ops, and Advanced (permission-dependent).
Console orientation
| Nav group | Examples |
|---|---|
| Overview | Dashboard, Analytics |
| Topology | Hosts, Clusters, Routes |
| Security | Policies, Rate limits, IP lists, Geo, Bot, Threat intel |
| Ops | Certificates, Config, Audit, Plugins, Users |
| Advanced | Gateway, API keys, Tenants, Notifications, SIEM, Challenges, IDS, ZTNA, Tunnel, SOC |
The Web app talks only to the API (ShieldGate:ApiBaseUrl). It does not access the database directly.
Verify
- Your user menu / profile shows the expected tenant.
- You can open Config (or any Topology page) without an API error banner.
Pitfalls
- Wrong tenant slug fails login even with correct password.
- If Web cannot reach API, check TLS trust and
ApiBaseUrl. - Browser clock skew can break JWT validation in edge cases.
Next
Build your first protected app path: First proxy overview.