Better way to catch authentication errors?
See original GitHub issueIs there a better way to catch authentication errors? At the moment if I run nexmo.initialize(...)
with incorrect credentials the callback for a method does NOT return an error
object. Instead the response
object looks as follows:
{ 'error-code': '401',
'error-code-label': 'authentication failed' }
There’s a few things that would be useful here.
- Catch authentication errors and actually return an error object instead of a response in an API call.
- Provide a way to validate
nexmo.initialize(...)
without making an API call
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Error Handling Best Practices - Auth0
Error Handling Best Practices · Send error logs to an external service · Use error objects in rules · Use meaningful error code...
Read more >WiFi Authentication Errors and Methods to Solve Them - Okta
How to fix a WiFi authentication problem · Forget the network. Head to WiFi settings on your device, find the network you're trying...
Read more >Handle spring security authentication exceptions with ...
The best way I've found is to delegate the exception to the HandlerExceptionResolver @Component("restAuthenticationEntryPoint") public class ...
Read more >Error Handling | Firebase Documentation - Google
The Firebase Authentication SDKs provide a simple way for catching the various errors which may occur which using authentication methods.
Read more >Handle errors and exceptions in MSAL.js - Microsoft Entra
Most errors that come from the library will be ClientAuthErrors. These errors result from things like calling a login method when login is ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I meant check that the credentials have been supplied - not that they existing within the Nexmo platform e.g. check for empty strings, null/undefined values and so on.
Irrelevant due to many changes since this was opened.