Frequently Asked Questions

Is your solution scalable?

Yes. Our REL-IDgateway has been scaled across millions of users by large financial institutions over the past two years. We’ve built it for performance and for Internet and IoT scale deployments.

Does your solution really close out the SSL vulnerabilities?

Yes. TLS/SSL has structural issues, typically around the third-party authorities in the certificate trust chain. Even with a perfect implentation of SSL, these vulnerabilities cannot be avoided. Self-signed certificates have become one alternative to third-party a priori trust, but the mechanisms of certificate delivery and diversity are still subject to scaling issues. REL-ID resolves both the structural problems of SSL while also creating the two-way uniqueness that two-way, self-signed SSL implementations have been attempting for years and have yet to easily deliver. Moreover, the way that REL-ID connections are established makes the protocol itself equivalent to or faster than SSL.

Is your solution difficult to implement in our environment?

No. REL-ID currently operates with applications connecting to gateway servers that sit in your enterprise DMZ. APIs are exposed from the REL-IDgateway Integration Server that can make any enterprise-side application into a REL-ID “aware” application, using the appropriate authentication, keys, and scopes for that application. Should an enterprise not want to use the default identity store inside the REL-IDgateway, the gateway server also exposes an LDAP BIND capability for bringing existing identity stores like ActiveDirectory into the REL-ID authentication process.

Is your solution too complicated for developers?

REL-ID has been built from the ground up with developers in mind. The Uniken engineers have created an endian-neutral, ANSI-C library of all the core functionality of REL-ID. They then built wrappers for each platform in order to do best-of-breed device fingerprinting for each type of device. Developers can take these device-aware SDKs and build them into any mobile or desktop application with a common set of API definitions and functions. Moreover, REL-IDmobile and REL-IDdesktop are being offered as open-source, javascript-based reference applications using the same REL-ID core libraries that we offer to our clients and their developer teams. We didn’t just build a secure communications SDK -- we built an open-source product around it. With ReactNative and Electron as the UI/UX frameworks, the time-to-market for new products with REL-ID security comes down from months to weeks.

Will your solution work well with other security tools and investments we have made?

Our REL-IDcore (the SDK) was built to provide absolute flexibility for clientside integrations and toolkits. We have already integrated many authentication toolkits into the REL-ID framework and are enhancing that list with the best-of-breed biometrics, set to be rolled out in the next REL-ID release. We are also planning to roll out a FIDO integration of REL-ID, in order to standardize the way that third-party toolkits can operate with the REL-ID SDK.

The REL-IDgateway has been built to provide flexibility with regard to both identity storage, like ActiveDirectory, as well as secure application connectivity inside your enterprise. We have identified a shift towards SaaS integrations and are building specific SAML/OAuth2/OpenID Connect capabilities into the REL-IDgateway. With this new flexibility, REL-ID can provide secure authentication from any device, as well as a Single-Sign-On experience with any third party application, all inside the REL-ID secure channel.

7 World Trade Center
250 Greenwich St
New York, NY 10007
466 Southern Blvd
Chatham Township, NJ 07928
3 Shalem St.
Ramat Gan, Israel
Teerth Technospace
S. No. 103
Mumbai Banglore Highway
Baner, Pune
Maharashtra 411045, India
Phone Numbers
+1 212 520 2557
+1 844 33-RELID
+1 844 337-3543
+972 (72) 2433000
+972 (72) 2733379 (f)
Hong Kong:
+852 6417 4790
+91 20 6725 3900