How is the Ignition Portal deployed?
Ignition Portal is deployed as an in-line device, with traffic flowing in one of its ports and out the other. This ensures that all traffic will have to be authenticated and authorized before it is allowed through.
Where would I deploy the Ignition Portal?
Generally, Ignition Portal is used as a gateway in public or shared areas in organizations: training rooms, conference rooms, open areas.
How does the Ignition Portal work?
Ignition Portal acts as the DNS and DHCP server for guest machines coming on the portion of the network it serves. When the user first fires up her browser, DNS will resolve all website hostnames to the login page on Ignition Portal, forcing the user to login. Once the user’s credentials have been validated and authorized, DNS will work normally, resolving to actual host IP addresses. In addition, a second security check is performed, so that no traffic can flow outside from the guest machine until the user has been authenticated.
Can both employees and guest users use Ignition Portal?
Yes. The tight integration between Ignition Portal and Ignition Server allows configuration such that employees can be authenticated as they come through the portal as well.
Does Ignition Portal work in a layer 3 network?
Yes. Ignition Portal can support both layer 2 and layer 3 networks. In layer 2 mode, the MAC address is used to associate the guest machine with a user ID. In layer 3 mode, the IP address is used to associate the guest machine with the user ID.
Can I make the login page look like my corporate web page, with appropriate branding?
Absolutely. Ignition Portal is designed for easy customization by our users. Most of our deployments have branded login pages, with appropriate legal language regarding terms of use that are specific to each organization.
Still have unanswered questions? Let us put you in touch with a solutions specialist today that can answer all your questions about the Identity Engines Ignition Portal.