Device Connectivity When User Deleted And Created In Another Account

[LeoNerdoG]

If Kura device is conencted to Kapua with certain user/account/password credential, but then this user is deleted and create in another account with same name and password (and with proper permissions), device (if reconnected) is seen in Connections tab.
This can be problematic (from my point of view) since user may not know what this device is, so it can bring confusion into the system. I know the device is only seen in "Connections" and not in "Devices" but nevertheless the question stays the same.
Is this proper behaviour or not?

Testflow:

1. Login as kapua-sys or any other user that has proper permissions
2. Go to Users, create user0 and add ALL:ALL:ALL:YES permission to it
3. Connect a live Kura device to user0:

• topic.context.account-name: kapua-sys
• username: user0
• password: --password of user0--

4. Now delete user0, go to Child Accounts and create an account (e.g. account0)
5. In account0 create user named user0 (same name as before) with ALL:ALL:ALL:YES peermission
6. Disconnect/Connect device if it does not reconnect itself
7. Login as user0 and go to Devices/Connections
   Observe how device is shown in Connections but not in Devices (this is OK, but should device really be shown in Connections?).

Expected behavior
I do not know what expected behaviour here is but should device really be visible in Connections view of user0 if this user is first created in one account, deleted and then created in another account?

Version of Kapua
1.1.0-SNAPSHOT

Type of deployment
[ ] Local Vagrant deployment
[x] Docker
[ ] Openshift (in its variants)
[ ] Others

Main component affected
[x] Console (in case of console please report info on which browser you encountered the problem)
[ ] REST API
[ ] Message Broker
[ ] - Others

Browsers used:

• Google Chrome (Version 72.0.3626.119 (Official Build) (64-bit))
• Safari (Version 12.0.3 (14606.4.5))
• Mozilla Firefox (65.0.1 (64-bit))
• Opera (Version:58.0.3135.79)