View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006181 | SOGo | Backend General | public | 2026-03-11 20:38 | 2026-03-12 07:35 |
| Reporter | yummiweb | Assigned To | qhivert | ||
| Priority | normal | Severity | block | Reproducibility | always |
| Status | feedback | Resolution | open | ||
| Platform | Proxmox VE | OS | Nethserver 8 | OS Version | PodmanContainer |
| Product Version | 5.12.4 | ||||
| Summary | 0006181: SOGo OpenID Problem - Redirect URI? | ||||
| Description | Dear SOGo Team, While setting up OpenID login for SOGo, I noticed that the required SOGo redirect URI isn't mentioned in any of the instructions. That's why I'm reporting this here, so that this information can be added to the instructions. As an alternative, I looked up the address in the compound URL of the link that initially leads to the OpenID provider. For example, it looks like this: Buit, isn't something missing? And if I enter this address as the redirect URI in the OpenID provider anyway, the OpenID login process logically results in a redirect loop (which eventually terminates). As a workaround, I then enter this address as the redirect URI in the OpenID provider. Unfortunately, I haven't found anything useful about this problem in the mailing list—only the aforementioned non-functional URIs. Could someone please confirm what a correct redirect URI would be? Or what else should I consider? My SOGo is version 5.12.4 (build@9a1f640bd211 202511171326) and is running as a container within a Nethserver 8 container orchestrator. Otherwise, SOGo is a great piece of software and has been running very reliably for years—excellent! Regards, Yummiweb | ||||
| Tags | authentication, identity, oidc | ||||
|
Correction to the link derived from the compound URL: "https://sogo.domain.tld/SOGo/" Regards, Yummiweb |
|
|
...and again the same error occurred after submitting (it looked correct while editing), so please disregard the """ at the end of the link. |
|
|
please disregard the " at the end of the link |
|
|
Unfortunately, I can't even enter " & q u o t ; " here... |
|
|
Hello, After you successfully ogin within your openid login page, if you have an infinite loop, it probably means that the email returns by your openid usersession does not match any uid in your user source (ldap/sql) server. SOGo not auth -> redirect to openid -> login to opend id -> redirect to SOGo -> fetch usersession and gte "email" param -> look for email in your user source -> don't find it = user not auth -> redirect to openid -> opendid user already logged in -> redirect to SOGo -> ... (Again not a good design but to make it correct, we would need to completely redo it. Oh wait... SOGo 6?!) To debug that add this to your sogo.conf: You can give it a go, give the log and your sogo.conf (mind the passwords in it) |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-03-11 20:38 | yummiweb | New Issue | |
| 2026-03-11 20:38 | yummiweb | Tag Attached: authentication | |
| 2026-03-11 20:38 | yummiweb | Tag Attached: identity | |
| 2026-03-11 20:38 | yummiweb | Tag Attached: oidc | |
| 2026-03-11 20:45 | yummiweb | Note Added: 0018425 | |
| 2026-03-11 20:47 | yummiweb | Note Added: 0018426 | |
| 2026-03-11 20:48 | yummiweb | Note Added: 0018427 | |
| 2026-03-11 20:50 | yummiweb | Note Added: 0018428 | |
| 2026-03-12 07:35 | qhivert | Note Added: 0018429 | |
| 2026-03-12 07:35 | qhivert | Assigned To | => qhivert |
| 2026-03-12 07:35 | qhivert | Status | new => feedback |