Single Connect GUI Configuration

configurations in the single connect gui are required as well create users and user groups (see sections docid\ mclwu52xvzwcvx1u g0c7 and docid 8e2jbctfdgt6 kubeput ) create device groups and add new devices to device groups (see sections docid\ b6bqxl4kuurptvciyenrn and docid 85rfh6qvfmgy6uzb4u6jr ) create device group realms with the user groups and device groups defined in the previous steps (see section docid\ b6bqxl4kuurptvciyenrn ) the devices added in step 2 must correspond to the last destination ip that sends an authentication request to single connect for example, wireless lan controller, firewall etc define the authenticator secret key as globalsecretkey on the device group properties (see section docid\ u58lwu6ckoaxj9 vkavdw ) navigate to administration > radius 802 1x config choose an eap typ e (only peap is currently available) fill in the fields “ certificate authority pem ”, “ certificate private key pem ” (which includes certificate and private key), and “ certificate private key password ” if dynamic vlan and mac filtering are to be activated, the box(es) should be checked (see section docid\ arrbswofyurng2fofttes ) vlans can be dynamically assigned by a radius server to applicants requesting 802 1x authentication through that server if dynamic vlan is assigned to applicants, the following 2 settings must be set in single connect check the dynamic vlan box in the 802 1x config screen the radius attribute policy should be defined on the related user group as vlan interval see section docid\ awuedduw8ogn4cl2kngsq check the add single connect server to active directory box and fill in the required fields