Using the same keyname on the same deployment but different product fails

[wvangeit]

Is there an existing issue for this?

• I have searched the existing issues

Which deploy/s?

production aws (e.g. osparc.io)

Current Behavior

on sim4life.io/.science, but I guess it will happen everywhere. The API key name by the user cannot be used on the same product. Creating the key fails without a real warning, and the key can't be used (although it can be copied to the pasteboard)
See:

Screen.Recording.2025-07-15.at.16.31.53.mov

Expected Behavior

User API keys are independent of product/deployment.

Steps To Reproduce

Create an api key with a certain name in one product.
The same name can't be used on the same deployment, different product.

Anything else?

No response

[giancarloromeo]

Quickly checked,

This constraint is the issue, perhaps we can relax it.

[pcrespov]

Options:
-1. Appending 1, 2, 3 etc to enforce uniqye display names
-2. Add in UI date of creation + expiration (so it displays the same name but you see that it is different entry)

I think your solution is ok but together with option 2.

[giancarloromeo]

What about adding the product to the uniqueness party. We don't allow the same display_name, for the same user on the same product.

[wvangeit]

@giancarloromeo 's solution indeed seems a bit more sustainable.

[pcrespov]

@giancarloromeo go ahead the.