ID 521884 - Allow Nuke login based licensing to use multiple system IDs

Problem summary
Allow login based licensing to write multiple System IDs

Currently the login based license system uses a single ID and if this is no longer recognised as a primary ID you need to log in again, even if it is still showing as a valid ethernet ID on the machine. RLM will still run if the mac address is showing, even if it is not the primary ID.

This will allow greater flexibility if the customer has a non-default ethernet set up.

Customer reported version
Nuke indie 13.2v4

Customer reported platform
Windows 11

Steps to reproduce

1) Check what the initial ID that is returned via ipconfig /all or ifconfig

2) Launch Nuke Indie, NC or Nuke commercial 14.0v1

3) Activate the login based license via the UI

4) Close Nuke

5) Disable the device providing the primary ID

6) Launch Nuke and you will need to log in again (which isn't possible if not connected to the internet)

Expected behaviour
Nuke should run for up to 37 days offline. If the login license system took multiple ethernet ids into account, if one was to be disabled or was no longer the primary, the lic code could recognise the other IDs.

Actual behaviour
Nuke wipes the license as it is seen as invalid and you need to reconnect the device providing the ID.

Workaround
Ensure Nuke is activated on a primary system id that wont change

Reproduced by support

This bug has been reproduced in:
Nuke 14.0v4
Windows 10 Proffesional

Earliest version tested
Nuke indie13.2v2
- It was not possible to back test indie/non commercial due to the build expiry

We're sorry to hear that

Please tell us why