FormidableLabs / FormidableLabs/react-native-app-auth

Additional Parameters not being sent on authorize request with OpenId scope

Ouverte
#822 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
Java
Étoiles
2.3k
Forks
473
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

## 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..

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Commencez par suivre la manière dont la requête authorize gère additionalParameters lorsque le scope openid est présent, puis comparez-la avec la gestion de la logout URL décrite dans l’issue. Le travail est terminé lorsque le paramètre tenantId est inclus lors de la récupération de la configuration OpenID, sans casser le flux authorize existant.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
ios, react-native
Domaine
authentication, mobile
Type d'issue
Bug
Difficulté
3/5
Temps estimé
1-2 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
45/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.