authentication - Same API, different authorization...is that managed with versioning?

Question

If an non-authenticating internal service is also published to an external audience, and authentication is desired in the latter situation....then the same service will need to be called with authentication from one client group, and without authentication from another client group.

Is the best practice to:

1. rename the endpoints, so one has authentication and one doesn't (that would mean that one of the endpoints has a less than perfect path)
2. use versioning in the path
3. some other strategy

question from:https://stackoverflow.com/questions/65836777/same-api-different-authorization-is-that-managed-with-versioning

Answer 1

Waitting for answers