Iván Valdés Castillo

Closing, as https://github.com/etcd-io/etcd/issues/18548 supersedes this issue. I'll update the CHANGELOG once we close the 3.4 and 3.5 pull requests.

This was discussed during the community meeting. I'll draft a document to discuss options for implementing this change.

I'm sorry it took me a very long time to draft the previously mentioned document. Here's the draft: https://docs.google.com/document/d/1Vpb0SosYT05YsBsgfJFzOAbSgitd1BcFOQzjEARaQyM. @ahrtr, PTAL and let me know your thoughts.

I'll start by breaking this up into smaller tasks. After that, I'll try to recruit some people to help. Then, we'll be able to proceed with the branch and pause...

After our discussion, I attempted to create the workspace without the tools module(s), but ultimately, it failed. I couldn't find an easy way to make it work this way. I...

Sorry, I was busy the last few weeks. This is next on my to-do list :)

@cruvie, please try using `rpctypes.ErrUserNotFound`. However, I think instantiating the client should return an authentication error before it gets to `client.AuthStatus`

@cruvie, got it. The issue is that I'm not able to reproduce. If I start a new cluster, enable authentication, and then run the snippet you provided: ```golang client, err...

Good catch, @cruvie. I added a unit test to confirm we're not wrapping up the errors. I have a fix for it, too. ```patch diff --git a/api/v3rpc/rpctypes/error_test.go b/api/v3rpc/rpctypes/error_test.go index bf3e0c680..3f95265dd...

A workaround right now would be to do the following: ```golang err.Error() == rpctypes.Error(rpctypes.ErrUserNotFound).Error() ``` There are still some integration and e2e tests failing in my PR that I'd need...