Directory Services and Directory Aggregation
Bring your own directory from any vendor and connect it to the Transmit Identity Services Hub or just enable the built-in LDAP-based directory that is already included in the Transmit platform. You can also connect multiple directory services and easily orchestrate them using Transmit’s orchestration engine, which completely isolates your applications from any directory service you chose to work with. Using Transmit platform, you can switch between directories, consolidate directories, route between directories based on any attribute, and combine on-premise and cloud directory services with no impact on your applications. Transmit also includes modern APIs which can be used to access directory information as an alternative to LDAP.
Transmit includes a built-in a directory server that implements a wide range of Lightweight Directory Access Protocol and related standards, including full compliance with LDAPv3 but also support for Directory Service Markup Language (DSMLv2). Written in Java, the Transmit LDAP offers multi-master replication, access control, and many extensions.
SQL and NoSQL Operational Database
LDAP is a relatively old technology, designed and built years before technologies such as mobile devices, IoT and RESTful APIs emerged. As such, the LDAP technology is not a good fit for storing information about devices, sessions, or even advanced entitlement models. Transmit includes an operational database based on either SQL or NoSQL which sits next to your directory. The Transmit Platform automatically stores more advanced information in the operational database thus avoiding the scalability issues many organizations are facing with directories.
Transmit provides a full set of authentication services to manage primary login, multi-factor, and step-up authentication across various applications and channels. The platform includes a large set of built-in authenticators such as OTPs, soft tokens, biometric authenticators, and knowledge-based authenticators. In addition, the platform can be used to manage any third-party authenticator or authentication service connected to the Identity Services Hub. Transmit’s authentication services manage the enrollment process for each authenticator and also tasks such as de-enrollment, re-enrollment, and expiry periods. The platform provides flexible ways of defining authentication levels and attaching them to different authenticators and journeys. The platform allows building rules for authentication failures across different authenticators and devices and taking various actions when thresholds are reached. Transmit is FIDO certified and can be used to manage any FIDO authenticator alongside non-FIDO authenticators.
KYC and Identity Proofing Services
Transmit is capable of activating numerous KYC and identity-proofing tools, such as scanning a government identity card and comparing the photo on the card to a live video stream of the user’s face. The platform can also access third-party databases for identity validation. For example, accessing a network operator’s data and verifying that the phone number provided by the user correlates with their details, such as name and address, in the phone company’s records. Using the Over-the-Air Journeys technology, onboarding journeys can be designed and implemented without writing code. The platform also allows building forms that collect information from the user during the KYC process as well as asking for various consents. The platform can then store identity-related information in identity stores and also generate credentials for the user and register the user for advanced authentication techniques.
Over-the-Air Journeys is the technology that sets Transmit apart from all other vendors. Using Over-the-Air Journeys, application owners can use graphical tools and an orchestration language to design simple and complex user journeys that involve authorization, authentication, KYC, fraud prevention, regulatory requirements, and more. Once done, these journeys can be pushed "over the air" and played in any application that is connected to Transmit, without making any code changes to the application and without the need to re-publish the application. Over-the-Air Journeys consist of two main technologies - a Journey Player and an Orchestration Engine. The Journey Player is incorporated into your applications as an SDK and is responsible for playing the entire journey inside the application. The Journey Player works with the Transmit Orchestration Engine which orchestrates the journey and defines the next steps on either the client or server side.