I really second this. As a Service Provider, the inability to filter on client public IP poses a security threat to us as we need to disable 2FA for known public IP addresses of our customers, not for their private range. If we create an exclusion for the range 192.168.1.0/24 because a customer has this on his subnet, it would allow anyone to bypass the MFA by just having the same subnet range on their computer..
coming in v21.0 is the ability to capture the client Public IP and pass it to RADIUS. More will come from this feature in the future. You can find out more and access the tech preview of v21 here: https://www.parallels.com/blogs/ras/whats-new-in-parallels-ras-21-0-and-why-its-important/
Parallels RAS v22 has been released and now allowes Public IPs to be used as filters for MFA. This allows excluding or including specific publlic IP adresses when enforcing MFA.
Support for SAML as a Multi-Factor Authentication (MFA) provider. This allows administrators to enforce SAML authentication as a mandatory secondary factor after initial Active Directory validation.
See https://kb.parallels.com/en/131219 for the full release note list.
@Karsayor
Support for SAML as a Multi-Factor Authentication (MFA) provider. This allows administrators to enforce SAML authentication as a mandatory secondary factor after initial Active Directory validation.
See https://kb.parallels.com/en/131219 for the full release note list.
@Karsayor