Identity for ITFortal products
One issuer. Every app, every role.
Sign-in, organizations, roles and policy documents behind a standard OpenID Connect issuer, with a Scalar-documented API to run it. Plans are billed through Consola Central.
$ curl -X POST https://iam-test.extremegym.com.mx/connect/token \
-d grant_type=client_credentials \
-d client_id=billing-worker \
-d scope=organizations:read \
-d resource=https://iam.itfortal.com/api
{
"access_token": "eyJhbGciOiJSUzI1NiIs…",
"token_type": "Bearer",
"expires_in": 3600,
"scope": "organizations:read"
}
The product in use
Everything an identity provider should do, without a second dashboard
Each screen below is the admin portal that ships with the issuer. Customers administer their own organization; you administer the tenant.
Organizations
Customers run their own organization
- Members, roles, invitations with a seven-day link.
- Verified e-mail domains route sign-ins automatically.
- Logo and colour on the hosted pages, with a contrast check.
| Member | Roles | State | MFA |
|---|---|---|---|
| ana@acme.io | org-admin | Active | On |
| dev@acme.io | org-member | Locked | Off |
| ops@acme.io | org-member, auditor | Invited | — |
Authorization
Roles at any scope, policies with explicit deny
- Assign a role to a user or a machine client at tenant, organization, application or resource scope.
- JSON policy documents with conditions on MFA, IP range, time and request tags.
- Test a policy against an unsaved document before it goes live.
Deny explicit_deny
| Sid | Effect | Action | Conditional |
|---|---|---|---|
NoDelete | Deny | users:delete | no |
Applications
Clients that follow the rules of their type
- Confidential, public and machine clients; PKCE for every user-facing grant.
- Two rotating secrets, shown once, with an expiry warning 30 days out.
- Device flow for CLIs and TVs with eight-character codes.
- client_id
billing-worker- Type
- Machine
- Secrets
- 2 valid · one expires in 21 days expiring
- Grants
- client_credentials
Audit
Every sign-in, token and change, exportable
- Organization-scoped for customers, tenant-wide for you.
- Filters by type, actor, target and outcome; NDJSON export.
- Retention follows the plan.
| When | Event | Outcome |
|---|---|---|
| 11:42:07 | auth.login_succeeded | Success |
| 11:41:50 | auth.mfa_failed | Failure |
| 11:40:12 | token.refresh_reuse_detected | Denied |
Quick start
Register a client, get a token, call the API
1 · register
POST /api/v1/clients
{ "clientId": "billing-worker", "displayName": "Billing worker",
"type": "Machine", "grantTypes": ["client_credentials"] }Machine clients hold up to two secrets so rotation has no downtime.
2 · token
POST /connect/token
grant_type=client_credentials
&client_id=billing-worker&client_secret=…
&scope=organizations:readPlain signed JWT. Validate it with the discovery document.
3 · call
GET /api/v1/organizations
Authorization: Bearer eyJ…
200 OK { "items": [...], "next": "…" }Every write is audited; every error is an RFC 9457 problem with a stable code.
Get started
Start on the free plan. Move up when your organization does.
No card needed. Plans and prices are managed in Consola Central.
See plans and start free