Console restrictions based on FQDN not just IP address

[BillR]

It is great the console access can be restricted now, but for admins that have ISPs (or even internal networks) that assign Addresses via DHCP, this can be an issue when a new/different address is assigned.
One solution would be to be able to specify an FQDN and use DYNDNS (or dynamic IP registration internally) to automagically update the FQDN and thus allowed IP Address.

NOTE: The anywhere access issue may also be mitigated by the use of 2 Factor Authentication (2FA)

 

[eddv123]

Take a look at the 3CX v16 launch party video, not 100% but I'm sure recalling someone mentioning 2 factor authenticated on the questions part of the video:
https://m.youtube.com/watchv=Z421fw461qc

 

[BillR]

Thanks, I watched the Q&A part and also heard a comment about 2FA, but it seemed to be tied somehow to Active Directory?
I'd like to see a 2FA solution integrated into 3CX based upon TOTP/related RFCs (there are 2 threads on that topic).

 

[eddv123]

I guess you are referring to the ideas site? The more votes on these the higher the chances of them being added.