Can't trigger 409 when creating Clients with same name

[brian.edelman]

In the documentation for the management API there is a documented 409 response. I’ve found 2 conflicting answers on the support forums related to multiple clients with the same name.

Preventing duplicate client names

We would like to prevent duplicate client (app) names to prevent user confusion: there’s no reason why two apps should have the same name, since this is confusing to both the Auth0 Admins and in the Universal Login Screen. Is there a way to configure this to prevent duplicate client names? It would be good if Auth0 would prevent this. If we can’t prevent duplicate client names, we can use the Auth0 Management API. Is there a way to search clients by client_name or do we need to traverse the en…

and

Unique name for the application creation

Hi @ashish, Thanks for the resposne. Nearly I am expecting 3000 - 5000 applications will be created. The third party servers / machine has to access our resource servers (cloud-apis). For each applications, we will be creating an applications and details will be share with third-party to get the tokens. I have requirement to add the readable identifier as claim like (“AppID”:“com.org.analytics.app”). so currently I am adding these names to metadata for each app. So to avoid duplication acro…

is name actually unique? Or am I reading the documentation wrong?

[dawid.matuszczyk]

Hi @brian.edelman

Welcome to the Auth0 Community!

Thank you for posting your question. I see where the confusion comes from. Based on my knowledge, the 409 - Another client that exists with the same alias is connected to the client_aliases, which is a different parameter from the name (client name). To answer your questions, creating multiple applications with the same name is not prohibited. But there’s also a deploy-cli in which, due to the implementation, it’s prohibited to make an application with the same name.

https://auth0.com/docs/api/management/v2/clients/post-clients

Thanks
Dawid