Company A is purchasing Company B, and will import all of Company B's users into its authentication system. Company A uses 802.1x with a RADIUS server, while Company B uses a captive SSL portal with…

Simply enabling RADIUS and endpoint security on Company B's devices does not integrate them into Company A's 802.1x authentication framework - it does not migrate B's devices to use A's RADIUS server as the authenticator.

Enabling plain LDAP authentication on Company A's devices would require A to downgrade or alter its infrastructure to match B's older portal-based system, which is the wrong direction for an acquisition integration.

Enabling LDAP/TLS on Company A's devices is a marginally more secure variant of option B but still incorrectly shifts Company A's infrastructure to match Company B's model rather than the reverse.

Company A is the acquiring entity and its 802.1x/RADIUS infrastructure is the target authentication system. Enabling 802.1x on Company B's network devices brings B's network into compliance with A's existing standard, allowing B's users - once imported into A's RADIUS backend - to authenticate seamlessly using the same protocol. This avoids fragmenting authentication systems and leverages A's already-established infrastructure as the authoritative system.