Question re switch from legacy to stable - SOGo Login for users

SebS

Hello,

I wasn’t able to update to the “new” version earlier, I am however not quite sure about some implications:

Direct SOGo login is now disabled. All unauthenticated requests to /SOGo will be redirected to /.
Users must use the mailcow login.
Administrators can define whether a user should be redirected to the mailcow UI or SOGo after login.

All unauthenticated requests to /SOGo will be redirected to /.

This seems overly specific? What would be the case where it does not happen, users who stay/are logged in using a bookmark/direct link? Or is does it just mean that there’s simply the one login form for both now but the URLs remains as they are?

I am not entirely sure what the consequences are: Can users access EITHER SOGo OR the mailcow UI or they have some sort of “toggle” they can use no matter where I redirect them initially (SOGo as a default would be best for most users, I think)? I can’t imagine that it is anything but the latter, but I need to make sure before I roll this out even for testing.

Thanks and regards
Seb

esackbauer

SebS Or is does it just mean that there’s simply the one login form for both now but the URLs remains as they are?

Basically yes. You have to login via Mailcows UI, and you as admin can configure where the user should land first after login, in mailcows user UI or SOGo.
Users can switch by themselves once they are logged in. In Mailcows UI they see a “Webmail” button, and in SOGo you have in upper right corner a new wrench icon which takes you to mailcows UI.

SebS

thanks!