Vivek Pandey is there any way we could potentially deduplicate them?

James Dumay To avoid creating new credential, we can do it by computing hash of existing credentials in `git-domain` (minus credential Id) and then avoid creating new one if hash of given credential matches with the existing one. Problem I see with this approach is doing it correctly for different credential types. but I think its doable.

OTOH, I think there is workaround as well, user can always delete the duplicate ones from classic UI or simply don't create same credentials as new ones, chose that one from the drop down

Vivek Pandey I am thinking this might not be such a big deal considering what we have planned for Git read/write support soon (using SSH only credentials).

I am going to close this against that ticket and we can address it there.

This issue is still present in 1.2.4 - Cannot remove these credentials once added via blue ocean as they don't appear in the jenkins credentials area.

Darren Graham Blue ocean works on folder credentials. if you are creating pipeline using blue ocean the it creates a blueocean credentials folder and your credentials a re in there.