It is possible to set very complex configurations entirely from the graphical user interface.
Multiple authentication profiles allow to provide different authentication services simultaneously. Each profile can use several user identity databases to authenticate and authorize network clients. Identity sources include local user databases, local Certification Authorities and external LDAP servers.

Authentication profile establish RADIUS authentication services with particular characteristics and can additionally define an HTTPS authentication portals.
Profiles optionally establish authorization and session policies with support of session control through Change of Authorization (CoA) functionality. Policies can check RADIUS attributes, session parameters and client device type.

Authentication portals provide layer 3 authentication in which the user enters their credentials using its web browser to get access to the network. To automate the process of the user account creation, user auto registration with optional contact authorization is available.
Authentication portals are normally used to implement guest access. Client hardware address authentication can be enabled to prevent customers from having to re-authenticate during a period of time.

Digital identities generated by local Certification Authorities (CA's) are used to implement certiticate based authentication (TLS).
To automate the distribution and installation of the digital identities to the client devices, each CA can define an enrollment portal to provide client auto provisioning.

Authentications and sessions are shown in real time and you can get detailed information about the authentication method, the identity database used to authenticate the user and session data obtained through RADIUS accounting received from the access device such as the client IP address and the download and upload traffic.
Additionally, the request, reply and session RADIUS attributes can be examined for debugging.

Install 2 Passport servers to form a cluster with automatic syncronization of configuration, user databasses and CA directories.
Both servers provide authentication services but only the Primary one allows to modify the Passport configuration. The Primary server sets the configuration of the Secondary and when changes are made to the Primary configuration, it is automatically synchronized on the Secondary server.
If you configure the NAS (Network Access Server) or a load balancing device with the IP address of both Passport servers, if one Passport server becomes unavailable, the authentications can be done using the other Passport server:


We have implemented 4 extensive examples configurations in the user manual.
Therefore, ermitacode’s team will be pleased to help you and troubleshoot anything you need.






Although the devices used are configured with static IP addresses, it is necessary a DHCP service in the network segment in which the wireless clients are connected.
Download Passport through the macOS App Store
Download DEMO for a 30 days trial.
Find details and step-by-step instructions on how to use the software.