All have solutions for it and I can’t understand the resistance here
There is no resistance, we’re discussing why we came to the current design and trying to understand your (and other people) requirements, so we can better define the possible solutions and pick one or more. As you mentioned there are multiple possible solutions.
There is already another request to add multiple URI to a resource:
Another approach we are considering is creating an URL alias list. This would not be linked to the resource but to an account setting (or organization settings).
Let the user (as you mentioned on the client-side) make the decision how to show linked password to the entity.
If it’s different from the wildcard on the resource url, or alias list, then I’m not understanding what you mean. Do you have a link to the documentation of another product doing what your describing?
Cheers,