FormidableLabs / FormidableLabs/react-native-app-auth
Catch Authentication Failed error in B2C
- Lingua principale
- Java
- Stelle
- 2.3k
- Fork
- 473
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
## Issue
Hi All,
I am using the B2C authentication, here I could n't get the error or failure response when we using the invalid username and password. I was expecting that any of authorize response or exception in catch block. If I get any error response, I can log in to my server as like authentication failed.
```
try {
const config = {
issuer: url(),
clientId: clientId(),
redirectUrl: 'app://token/',
scopes: ['openid', 'offline_access', clientId()],
iosPrefersEphemeralSession: true,
};
const result = await authorize(config);
console.log('B2CResult -----***', result);
return result;
} catch (error) {
console.log('Consoeoooo ---*****>', error);
}

```
---
## Environment
* **Your Identity Provider**: `Azure B2C`
* **Platform that you're experiencing the issue on**: `iOS / Android / both`
* **Are you using Expo?** No
* **"react-native-app-auth": "^7.0.0-rc2",
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
No repository file or test is named. Start by reproducing the Azure B2C invalid-username-and-password flow around the authorize(config) call on iOS and Android, then trace whether it returns a result or reaches the catch block. Done means the observed failure behavior is established and the issue identifies the expected error response or a specific implementation location.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- android, ios, react-native
- Ambito
- authentication, mobile
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100