You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 20, 2024. It is now read-only.
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.
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)
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:
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):
*I removed the user from the database several times (from the
g_user
andgpr_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):
sso_prod.dump.sql.zip
P.S. SQL dump is redacted because I remove all sensitive data
The text was updated successfully, but these errors were encountered: