Closed folt closed 6 years ago
Thank you for your time.
Team RabbitMQ uses GitHub issues for specific actionable items engineers can work on. This assumes two things:
We get at least a dozen of questions through various venues every single day, often quite light on details. At that rate GitHub issues can very quickly turn into a something impossible to navigate and make sense of even for our team. Because of that questions, investigations, root cause analysis, discussions of potential features are all considered to be mailing list material by our team. Please post this to rabbitmq-users.
Getting all the details necessary to reproduce an issue, make a conclusion or even form a hypothesis about what's happening can take a fair amount of time. Our team is multiple orders of magnitude smaller than the RabbitMQ community. Please help others help you by providing a way to reproduce the behavior you're observing, or at least sharing as much relevant information as possible on the list:
rabbitmqctl status
(and, if possible, rabbitmqctl environment
output)Feel free to edit out hostnames and other potentially sensitive information.
When/if we have enough details and evidence we'd be happy to file a new issue.
Thank you.
I don't understand what problem that would solve. This plugin only needs a specific response from a backend, and provides a [mostly] fixed set of fields, of which username is certainly one. The demos are not meant to be used in production, they are only examples. Feel free to modify them as you see fit.
Hi! I encountered such a problem. I use Django for backend authentication using AUTH_USER_MODEL. So it turned out that I have my own user model and I use the "phone" field with USERNAME_FIELD. It would be nice to be able to specify in the settings field for username. This would be suitable for many development technologies.