Closed TehNeon closed 6 months ago
The default Redis username is "default". How did you produced this error? You are providing the Redis secret yourself and you don't know how to fill the username field?
(with the big protobuf crash, I'm terrified of having shipped another breaking release by mistake 🙃)
The default Redis username is "default". How did you produced this error? You are providing the Redis secret yourself and you don't know how to fill the username field?
(with the big protobuf crash, I'm terrified of having shipped another breaking release by mistake 🙃)
I wasn't aware that it used the username "default". That's totally my bad. Going to close this issue. I swapped my cluster over to specify the name as default and it appears to function. Whenever I've used Redis authentication (through Jedis) I've always used the constructor that only takes in the password, and with Redis clients I've always left the username field empty and I guess they also will then fill it in as default when not specified.
I could totally implement a fallback behavior to inject "default" if the value is not filled. That would be a good UX addition.
That's not a bad idea. Although currently there is no docs going over the Managed vs Provided Redis setup, which if they were made could also explain that to use the "default" user as well. Since I only found out about the feature from looking at the CRDS for MinecraftCluster.
What happened?
Currently the provided Redis feature doesn't allow you to not defined a username. Redis allows for usernameless authentication by just accepting a password. If you pass in an empty username it still attempts to authenticate with username-pass based auth instead of just password auth.
What components are involved in your issue?
Proxy Agent (BungeeCord), Proxy Agent (Velocity), Server Agent (Paper)
Version
0.8.1
Kubernetes Version
1.28.7
Relevant log output
Code of Conduct