[Issue] Segfault on oidc login flow after user registration #218

New issue

Open

opened 2023-07-25 19:28:45 +02:00 by roquie · 0 comments

roquie commented

2023-07-25 19:28:45 +02:00

(Migrated from github.com)

Describe the issue
Before user registration server works as expected. After registration of the first user I got a segfault with new and any created user before on oidc login flow.

Error from API Gateway:

{"errorMessage":"Get \"http://127.0.0.1:8080/api/example/auth?client_id=example\u0026code_challenge=D4iIgYoBCgkuOqddrYtQuzL9lwyJJQeSL40zihf-12c\u0026code_challenge_method=S256\u0026g_continue=\u0026nonce=static\u0026redirect_uri=https%3A%2F%2Fconsole.dev.example.com\u0026response_mode=query\u0026response_type=code\u0026scope=openid\u0026state=7ee73d7b23e84f2285512e3aa17c265c\": EOF","errorType":"HealthCheckError"}

Service logs at this moment (all logs for debug level):

/entrypoint.sh: line 8: 87 Segmentation fault glewlwyd --config-file=/etc/glewlwyd/glewlwyd.conf -mconsole -e -p $PORT

To Reproduce
These are approximate steps, since I have a segfault, I can’t look exactly (but I have sql dump):

Add an oidc plugin and configure it for public client (response type: code, id_token; PKCE enabled; RSA 256 keys)
Add a user registration plugin and configure: email as username, email verification enabled, etc
Enable registration within webapp config file
Register user and complete flow*
Log In and get segfault

*I removed the user from the database several times (from the g_user and gpr_session tables) and submitted the verification code several times. Also, once, I registered from the wrong host (a local service configured as "production" and connected to the "production" database) and got a kick from the backend.

System (please complete the following information):

OS/Environment: Docker, Qemu, Mac OS Ventura, M1 (arm)
Browser used: Chrome latest
Glewlwyd Version: 2.7.5
Source installation: Docker

sso_prod.dump.sql.zip

P.S. SQL dump is redacted because I remove all sensitive data

**Describe the issue** Before user registration server works as expected. After registration of the first user I got a segfault with new and any created user before on oidc login flow. Error from API Gateway: ```json {"errorMessage":"Get \"http://127.0.0.1:8080/api/example/auth?client_id=example\u0026code_challenge=D4iIgYoBCgkuOqddrYtQuzL9lwyJJQeSL40zihf-12c\u0026code_challenge_method=S256\u0026g_continue=\u0026nonce=static\u0026redirect_uri=https%3A%2F%2Fconsole.dev.example.com\u0026response_mode=query\u0026response_type=code\u0026scope=openid\u0026state=7ee73d7b23e84f2285512e3aa17c265c\": EOF","errorType":"HealthCheckError"} ``` Service logs at this moment (all logs for debug level): ```bash /entrypoint.sh: line 8: 87 Segmentation fault glewlwyd --config-file=/etc/glewlwyd/glewlwyd.conf -mconsole -e -p $PORT ``` **To Reproduce** These are approximate steps, since I have a segfault, I can’t look exactly (but I have sql dump): 1. Add an oidc plugin and configure it for public client (response type: code, id_token; PKCE enabled; RSA 256 keys) 2. Add a user registration plugin and configure: email as username, email verification enabled, etc 3. Enable registration within webapp config file 4. Register user and complete flow* 5. Log In and get segfault *I removed the user from the database several times (from the `g_user` and `gpr_session` tables) and submitted the verification code several times. Also, once, I registered from the wrong host (a local service configured as "production" and connected to the "production" database) and got a kick from the backend. **System (please complete the following information):** - OS/Environment: Docker, Qemu, Mac OS Ventura, M1 (arm) - Browser used: Chrome latest - Glewlwyd Version: 2.7.5 - Source installation: Docker [sso_prod.dump.sql.zip](https://github.com/babelouest/glewlwyd/files/12163983/sso_prod.dump.sql.zip) P.S. SQL dump is redacted because I remove all sensitive data

This discussion has been locked. Commenting is limited to contributors.