Wired SSO FAQ

wired sso configuration and behavior as an admin, do i have control over where and when wired sso is enabled? yes, the admin has control over where wired sso is enabled when creating a segment in the nile customer portal, there will be an option to enable the wired sso feature this feature can only be enabled if an identity provider (idp) has been configured in the nile portal alternatively, the wired sso configuration can be accessed through the "access management" > "wired sso" section, where the admin can enable the feature and select the onboarding and employee segments as an admin, what do i need to do to make wired sso work? as an admin, you'll need to complete the following steps to set up wired sso set up saml authentication with your identity provider (idp) create a dhcp scope with a short lease time (e g , 5 minutes) this ensures that devices release their ip addresses and get a new one when the segment changes create an "onboarding" segment and map it to the dhcp scope defined in step 2 identify the "employee" segment that authenticated users should be assigned to enable the wired sso feature in the nile customer portal and select the onboarding and employee segments when wired sso is enabled, nile will automatically create an "all" rule that applies the onboarding and employee segment assignments based on the sso authentication status what happens to devices that are not browser based and do not match any mac auth or oui rules? devices that do not match any mac auth or oui rules will be placed in the onboarding segment and marked as "waiting for approval" in the nile portal even though these devices are technically approved, they will not have access to the network due to the captive portal (sso) requirement the admin can manually approve these devices or, if the device can be fingerprinted and a fingerprint rule exists, it can be automatically moved to the appropriate segment in some scenarios, the device can also be registered through the self registration portal, which will authorize it while it's in the "waiting for approval" state can wired sso be enabled at certain locations only? no, wired sso cannot be enabled at specific locations only it is a global setting that applies to all locations where the configured onboarding and employee segments are used how often does a device have to authenticate via sso on the wired network? the device has to authenticate via sso in the following scenarios if the device has not connected to the network (wired or wireless) for 30 consecutive days if the device is seen on a different port than the one it was originally authenticated on (indicating a location change) if the user changes their password in the idp (nile needs to be notified of this event) once a device is authenticated, it is added to the mac auth table, and subsequent connections to the wired network will not require sso re authentication, as the device's mac address will be recognized what is an "onboarding" segment? the "onboarding" segment is a restricted network segment that only allows access to the customer's idp portal all devices that are not capable of 802 1x authentication or are not present in the mac auth table will be assigned to this segment and granted an ip address, but they will be blocked from accessing the rest of the network until they successfully authenticate via sso the admin cannot use the onboarding segment for other purposes, such as including it in an oui or fingerprint rule the segment must be dedicated to the wired sso onboarding process if an iot device is connected and is not in the mac auth table, will it get an ip address? yes, the iot device will get an ip address from the onboarding segment and will be marked as "waiting for approval" in the nile portal it will not have access to the network until it is authenticated via sso or manually approved by the admin what segment will the device be on after successful sso authentication? after a device successfully authenticates via sso, it will be moved from the onboarding segment to the employee segment configured during the wired sso setup if the user has previously connected to the wireless network and been assigned a segment, they will be placed in that same segment otherwise, they will be assigned to the employee segment defined in the wired sso configuration what is the priority of mac auth rules? when a device is connected to a wired port, the nile access service will evaluate the following mac auth rules in order exact mac address match fingerprint match (e g , polycom vvx 300) oui address match all / wired guest / wired sso the "all" and onboarding rules are mutually exclusive, meaning only one of them can be configured if a laptop is returned by a user, can we ensure it cannot access the network? from the mac auth table in the nile customer portal, the admin can delete the mac address of the user's device or delete the user's entry completely this will force the device to go through the sso authentication process again the next time it connects to the network what happens when an employee leaves the company? nile will integrate with the customer's idp to be notified when an employee leaves the company all of the employee's associated devices will then be removed from the mac auth table, ensuring they can no longer access the network what happens to ad login when a device is not authenticated via sso? the behavior of ad login for devices that are not authenticated via sso is still to be determined nile will need to evaluate whether ad ports can be allowed for authentication in these cases