eFTI requirements combine authenticated access, authorisation, confidentiality, integrity and detailed auditability because the data can be commercially sensitive and used in regulatory inspections.
The framework requires traceability of processing operations and preservation of relevant historical values when data changes.
Adminyra therefore has a dedicated per-data-element audit model in addition to general system events.
Customer API authentication, business-user authorisation and Gate-to-platform trust are separate security problems.
The portal can later supply identity context without becoming the authority-trust or freight-data boundary.
No. Adminyra treats central identity as an adapter while eFTI maintains local authorisation and regulated-data boundaries.
No. Adminyra eFTI is under active development. Production authority exchange stays disabled until the required interoperability, conformity-assessment and certification steps are complete.
Yes. Data mapping, sandbox API work, CMDS lifecycle design and application integration can be prepared before production Gate trust is enabled.
Start with a real freight-data mapping in the sandbox. Production Gate exchange remains locked until the certification and interoperability path is complete.