MOBILE-ID · TRUSTED LTANS
Design a Trusted LTANS PoC
Prepare data, scope, acceptance criteria and a summary for your evaluation request.
Design a bounded evaluation
This form creates a summary file on your device. It does not send information to Mobile-ID or store form entries on a server. Do not enter real customer payload or secrets.
After submitting a PoC request
| Step | Agreed output |
|---|---|
| Discovery | Record types, source, custody and decision owner. |
| Scope | Synthetic data, positive/negative cases, criteria and exclusions. |
| Provision | URLs, grants, trust context, byte channels and secure support. |
| Execute and reconcile | Retain requests/responses, Jobs, evidence, reports and errors. |
| Conclusion | Per-case PASS/FAIL/NOT_VERIFIED, remediation owners and go-live conditions. |
Provisioning and schedule are agreed after discovery; the website does not itself confirm receipt.
Add architecture test scope
In the PoC request confirm WSO2/Keycloak/Core versions, token method, audience/scopes, security profile, custody and byte channel. Distinguish validator/fixture results from gateway/backend and real cryptographic verification.