Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Who and where are you going to manage MAC addresses then?
Sorry, we are not going to implement this.
Agree with the development function, we often found that users randomly copy ID login, security policy will lead to password confusion, administrators often need to re-register processing, hope to bind MAC address, can prevent users randomly copy ID login problem!
This does not make any sense as the MAC address is only valid in your local LAN segment.
As soon as there is any router involved, Domino sees only the MAC of the router.
Typically Domino is the only service on a given piece of hardware / virtualware. Where I've seen customers do this, the approach is to block other IPs at the firewall, not at Domino. This prevents access at a much higher level than an individual piece of software. This is a much more secure and, in my opinion, better practice approach, using the right tools to control this business requirement.
In my opinion, there is no reason this needs to be delegated to Domino.