Re: Explicit specify bad username or password when using BasicAuthentication

2020-12-04 Thread Wilson Cazarré
Oh I see, guess I'll just drop that idea. Ty On Friday, December 4, 2020 at 4:26:03 PM UTC-3 steve...@mobileappbrewery.com wrote: > Typically, a more specific message is not considered good form because it > gives potential hackers a clue about what is wrong. > > —Steve > Steve Wehba > The Mob

Re: Explicit specify bad username or password when using BasicAuthentication

2020-12-04 Thread Steve Wehba
Typically, a more specific message is not considered good form because it gives potential hackers a clue about what is wrong. —Steve Steve Wehba The Mobile App Brewery steve.we...@mobileappbrewery.com 760-846-1082 On Dec 4, 2020, 11:24 AM -0800, Wilson Cazarré , wrote: > The current behavior of t

Explicit specify bad username or password when using BasicAuthentication

2020-12-04 Thread Wilson Cazarré
The current behavior of the DRF is given the message "Invalid username/password" upon bad authentication credentials to the API. Any thoughts on how to make the error message more explicit by specifying if was a bad username or password? -- You received this message because you are subscribed