Integration
Diagnostics
This call goes out from the CRM server with the organisation’s M2M token. There is no employee session involved: clear the cookies and it answers the same.
How this console talks to TripleEnable
- Who calls
- The server of this CRM, never the agent’s browser. Neither the M2M token nor the secret that requests it reach the workstation: it is checked by opening the network tab.
- Issuing
- POST /v1/b2b/credentials. The claims are composed by this server reading the roster record; only the customer identifier comes from the browser.
- Verifying
- POST /v1/b2b/presentations opens the session in TripleEnable’s verifier and returns the OID4VP link. This organisation has no verifier and no verification key.
- Alerting the mobile
- POST /v1/b2b/wakeups. The response is the same whether the holder has a wallet or not — deliberately: if it distinguished, it could be used to find out who has the app by trying identifiers — so it does not confirm that anything rang.
- Following a verification
- The ceremony screen polls this same server every 3 s and it is that server that queries GET /v1/b2b/presentations/:id. Three seconds and not one because the B2B gate carries a per-organisation rate bucket shared with issuing.
- The customer roster
- It does not leave here. It lives in this CRM’s own database and neither te-api nor Logto ever read it; the only thing that travels about a customer is what is signed inside their credential.
Local configuration
- Organisation
- bcl2seovm54p
- Name
- Larkfield Energy Ltd.
- Domain
- energy.demo-te.com
- did:web published
- did:web:energy.demo-te.com
- Official numbers
- +44 20 7946 0110 · +44 808 157 0110
- Brand
- #5b3ea6 #2e1f4a · LE
- te-api (issuing)
- https://te-api.idp.tripleenable.com
- te-api (verification)
- https://te-api.idp.tripleenable.com
- Customer portal
- no application declared · CRM_ORG_<SLUG>_PORTAL_CLIENT_ID y CRM_ORG_<SLUG>_PORTAL_CLIENT_SECRET
How the organisation is chosen
- Who chooses
- The domain the request came in on. Each organisation declares its own in CRM_ORG_<SLUG>_DOMAIN, and a single deployment answers on all of them.
- If the domain belongs to nobody
- CRM_ACTIVE_ORG_ID is used, which is a decision written by whoever deploys. In production it is not set: without it, an address that matches no organisation says so instead of showing the first one’s roster.
- The DID document has no fallback
- /.well-known/did.json answers 404 on a domain that belongs to no organisation. Serving another organisation’s document would publish its identity on a domain that is not its own.
Interface language
- Who chooses
- Whoever is looking at the screen, from the sidebar. It is stored in the crm_locale cookie and applies to this browser only: it does not depend on the domain, which is what identifies the organisation, and it does not need a redeploy.
- Active language
- en · English
- Fallback
- English. A key with no translation is shown in English; the key name is never painted on screen.
The CRM database
- Connection
- It answers.
- Customers of this organisation
- 2
What te-api says
- organizationId
- bcl2seovm54p
- legalName
- Larkfield Energy Ltd.
- did
- did:web:energy.demo-te.com
- token scopes
- credentials:issue verifications:request
- types it can issue
- customer (max. 365 d)