Ianum is a cloud platform for passwordless authentication and user data management. The strength relies in the use of smartphones and blockchain-inspired encryption, so that only those who have the keys can authenticate and see their data. This guarantees a secure system where Ianum acts as a guarantee layer, but has but has no access to unencrypted users' data.
Ianum Platform is made of a series of services, each one with its specific task. Microservices can be Personal Data Management when you need to ask for users’ personal data, Consensus Management, when during a login you would like to ask for consensus, as well as Passwordless Authentication, to let users login using their smartphone. Full list is available at www.ianum.com .
All these microservices can be used both internally within companies (they are SAML compatible) or towards end users (e-commerce login, etc.), as well as for GDPR compliant data management and data consent.
To connect Ianum services you need to create a Gate, that is a virtual connection between your services and Ianum Platform. Each gate has a unique identifier (unique URL) and it’s where users needs to go through to be identified.
Gates can be of 3 types:
- public: when you need to authenticate any users that try to access that gate. Example: e-commerce
- private: when you want only a specific list of users to be able to access that gate. ex.: backend application
- Identity Provider: same as private, but compatible with SAML 2.0 protocol, so to be used in any SAML 2.0 compatible business tool
In this article we will focus on the integration between SMA 12.3 Tunnel Access and a Ianum Identity Provider using the SAML 2.0 protocol.
To complete the connection you need first to configure the connection with Ianum , configuring it as an Identity Provider. Next step, you need to configure connection with SonicWall, so that users allowed by Identity Provider are accepted by SonicWall system.