Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Single Sign On feature for external apps broken #6226

Closed
5 tasks done
dirkpauli opened this issue Dec 22, 2024 · 3 comments
Closed
5 tasks done

Single Sign On feature for external apps broken #6226

dirkpauli opened this issue Dec 22, 2024 · 3 comments

Comments

@dirkpauli
Copy link

Contribution guidelines

I've found a bug and checked that ...

  • ... I understand that not following the below instructions will result in immediate closure and/or deletion of my issue.
  • ... I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
  • ... I have understood that answers are voluntary and community-driven, and not commercial support.
  • ... I have verified that my issue has not been already answered in the past. I also checked previous issues.

Description

I use mailcow as a single sign on provider for nextcloud. with the latest release, the oauth2-authentification of mailcow seems to be broken. instead of showing the page "authorize application" it redirects to the config page of the user, making a web login to nextcloud impossible.

This is how it behaves in 2024-11b. Reverting to git commit 9f7d965ea14035966a284082602655c3c3252e92 will make it work again, but blocking other updates.

Logs:

/

Steps to reproduce:

1) set up mailcow in commit 9f7d965ea14035966a284082602655c3c3252e92 and nextcloud in version 30
2) set up oauth authentification between mailcow and nextcloud as described in https://docs.mailcow.email/third_party/nextcloud/third_party-nextcloud/
3) check the authentification works in nextcloud web interface using mailcow oauth2
4) update mailcow to 2024-11b
5) try to authentificate in nextcloud using mailcow oauth

Which branch are you using?

master

Which architecture are you using?

x86

Operating System:

Debian 12

Server/VM specifications:

8 GB, 4 cores

Is Apparmor, SELinux or similar active?

irrelevant

Virtualization technology:

Docker

Docker version:

27.4.1

docker-compose version or docker compose version:

v2.32.1

mailcow version:

2024-11b

Reverse proxy:

nginx

Logs of git diff:

irrelevant

Logs of iptables -L -vn:

irrelevant

Logs of ip6tables -L -vn:

irrelevant

Logs of iptables -L -vn -t nat:

irrelevant

Logs of ip6tables -L -vn -t nat:

irrelevant

DNS check:

172.64.155.249
104.18.32.7
@mkuron
Copy link
Member

mkuron commented Dec 22, 2024

Confirmed. Happens on mine too. 9f7d965ea14035966a284082602655c3c3252e92 is not a commit in this git repository, so I assume you have local commits with local modifications. Could you please confirm which public commit that corresponds to?

@dirkpauli
Copy link
Author

ups - right, this is the git number locally from my update history.

I haven't done any local changes to the files.

Mailcow version must be from commit 37beed6; so version 2024-08a

@mkuron
Copy link
Member

mkuron commented Dec 23, 2024

Duplicate of #6161, which is fixed in 49e05f5 and will be part of the next release.

@mkuron mkuron closed this as completed Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants