FormidableLabs / FormidableLabs/react-native-app-auth
Additional Parameters not being sent on authorize request with OpenId scope
- Vorherrschende Sprache
- Java
- Sterne
- 2.3k
- Forks
- 473
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
## Issue
Hi! First time user of this library. I really like the simplicity of it although the lack of documentation in certain aspects makes it a little bit hard to wrap your head around sometimes.
As the title suggests I've been trying to make an authorize request using FusionAuth as my OpenID provider but it doesn't work, it kept throwing an error that said "issuer mismatch". Investigating further lead to the core issue, I have multiple tenants in my configuration and the fushionauth provider gets the first one by default, turns out I need to add a tenantId parameter to the request to differentiate between the default and the specific tenant that we want to use, so I added this id as an additional parameter (look below for my configuration). I've already checked and when I try to logout the URL does contain the `tenantId` parameter so this probably is an issue of the authorize path only.
```js
export const FUSIONAUTH_CONFIG = {
...
additionalParameters: {
tenantId: "tenant id"
},
scopes: ['openid'],
};
```
I expected the library to change the following request for the OpenId configuration
https://{issuer domain}/.well-known/openid-configuration
To
https://{issuer domain}/.well-known/openid-configuration?tenantId={tenant id}
Instead it kept trying to retrieve the configuration from the default tenant.
---
## Environment
* **Your Identity Provider**: FusionAuth
* **Platform that you're experiencing the issue on**: iOS
* **Are you using Expo?** Yes..
Beitragsleitfaden
Rechercherichtung
Beginne damit nachzuverfolgen, wie die authorize-Anfrage additionalParameters behandelt, wenn der openid-Scope vorhanden ist, und vergleiche dies anschließend mit der in der Issue beschriebenen Behandlung der logout URL. Als erledigt gilt die Änderung, wenn der Parameter tenantId beim Abrufen der OpenID-Konfiguration enthalten ist, ohne den bestehenden authorize-Ablauf zu beeinträchtigen.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- ios, react-native
- Bereich
- authentication, mobile
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 45/100