FormidableLabs / FormidableLabs/react-native-app-auth
Additional Parameters not being sent on authorize request with OpenId scope
- Lenguaje dominante
- Java
- Estrellas
- 2.3k
- Forks
- 473
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
## 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..
Guía de contribución
Línea de trabajo
Comienza rastreando cómo la solicitud authorize gestiona additionalParameters cuando está presente el scope openid y, después, compáralo con el manejo de la logout URL descrito en la issue. Se considera terminado cuando el parámetro tenantId se incluye al recuperar la configuración de OpenID, sin romper el flujo authorize existente.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- ios, react-native
- Área
- authentication, mobile
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 45/100