Appearance
Sign-in, SSO and API keys
BMA signs people in to one organization at a time. Each organization chooses which sign-in methods it accepts; BMA staff set that up for it. Systems don't sign in as people: they call the Tenant API with an API key, or, for a marketplace host, the host API with a host key.
Sign-in methods
| Method | How it works | Set per organization |
|---|---|---|
| Password | BMA checks the user's own password (stored as a one-way hash). | on by default; can be switched off |
| LDAP or Active Directory | BMA binds to the organization's directory with the user name and password typed on the sign-in page. | server, port, TLS or SSL, base DN, service account, user filter or DN pattern, AD domain |
The sign-in page sends the user to Google (OAuth 2.0 authorization code, scope openid email profile) and back. | client id and secret, allowed email domains |
All three end the same way: MFA if it applies, then a new session.
Which organization
The sign-in page sends the organization's code with the user name and password (tenant_code). The shell reads it from the address: …/next/#/login?tenant=<code>. With no code, sign-in goes to the install's default organization. An organization can also have its own hostnames: on one of them, sign-in belongs to that organization and a code for another organization is refused.
A user who belongs to more than one organization signs in to one, and can switch inside BMA.
New users from a directory or Google
Both LDAP and Google can create the BMA user on first sign-in (auto_provision), in a group the organization chooses (default_group_id). Without it, an administrator creates the user first and the directory or Google only proves who they are. Google can be limited to email domains (allowed_domains, exact match on the domain).
Google sign-in needs an address Google has verified. Neither method lets someone into an organization they don't belong to: a user of another organization, BMA staff and the Administrator group are refused (Account not enabled for this organization).
MFA
BMA's MFA is a time-based code (TOTP: 6 digits, every 30 seconds) from an authenticator app, with 10 single-use recovery codes.
- The organization's mode is
off,optionalorrequired. A user's own policy (set by an administrator) wins over the organization's:inherit,required,optionalordisabled. - Someone who has set up MFA is always asked for a code, whatever the mode.
- When the mode is
required, a user without MFA sets it up during sign-in, before they get in. - Directory and Google sign-ins get the same MFA step.
People's side of this is in Sign in and MFA.
Sessions and CSRF
A signed-in browser holds a session cookie (ACNEXTSESSID by default): HttpOnly, Secure on HTTPS, SameSite=Lax. There are no bearer tokens for people and no "remember me". The session ends when the user signs out or when it has been idle longer than the server's session lifetime. The session id changes when someone signs in and when BMA staff start or end "view as". Sign-ins, refused sign-ins and sign-outs are kept in the audit trail.
Every change (POST, PUT, PATCH, DELETE) must send the session's CSRF token in an X-CSRF-Token header. See API conventions.
API keys and the Tenant API
An organization's systems reach its App Builder data through the Tenant API:
http
GET /api/index.php/tenant-api/v1/<organization code>/<route code>?q=drill
X-Tenant-Api-Key: tak_…- Keys start with
tak_. They are shown once when made, and BMA keeps only a hash. - A key belongs to one organization and works only in that organization's address.
- A key has scopes:
query:run,table:read,table:write,workflow:run,files:read,http:proxy. Authorization: Bearer tak_…works too. No session and no CSRF token are involved.
Making keys, routes and errors: Tenant API.
The marketplace's own sign-in
The marketplace module has its own ways in, apart from BMA's sign-in page:
| Who | How |
|---|---|
| A host's users, inside the host's platform | the host signs a short-lived token with its SSO secret; the marketplace swaps it for a marketplace session (Embed) |
| A host's own systems | the host API key (mph_…) (Host API) |
| Host and vendor staff in the portals | BMA sign-ins, with roles in the host or vendor account |
What BMA does not support
Say so plainly to anyone who asks, rather than promise it:
- No SAML. There is no SAML service provider in BMA.
- No generic OpenID Connect. Google is the only redirect-style provider, and its settings are Google-specific. Microsoft Entra ID (Azure AD), Okta and other identity providers can't be connected through OIDC today. Active Directory works through LDAP.
- No SCIM or other directory sync: users are created on first sign-in (if
auto_provisionis on) or by an administrator. - No SSO into BMA's own shell from a host platform. The host SSO token signs people in to the embedded marketplace only.
- No personal access tokens for people. Systems use Tenant API keys.
A new identity provider is added in BMA's core code, by BMA. If you need one, ask BMA staff.