Multiple JMX Credentials for a target JVM with the same target alias

[maxcao13]

Wondering, is it intended for the deletion of a JMX Credentials to delete all credentials for the same target?

If I also navigate away, it will also delete extra credentials of the same target, leaving only 1 of them regardless if the actual username and password were different or not.

[andrewazores]

You're only meant to be able to store 0 or 1 sets of credentials for a target. The targetId is used as a unique key for this, like we have done elsewhere, so if you have "aliased targets" where more than one targetId's JMX URL points to the same actual JVM instance, then you can do weird things. Though in that case, the credentials used will simply depend on which URL you use to access the target JVM.

It sounds like you're describing a graphical bug where the table displays more than one row for a given JVM target?

[maxcao13]

Right, I think the UI should just not let you create more than 1 set of credentials for each target then, because people are able to do that right now, not that it really affects anything other than, like you said a graphical bug.

[andrewazores]

I believe it'll end up overwriting the previous credentials on the backend when you do that, which I think makes sense. But the table is supposed to remove the previous entry and replace it with the new one when you do that. Sounds like that's been broken, but #465 will happen to fix this bug anyway since the table is getting redone.

[maxcao13]

Gotcha, thanks!