Just performed a full update this evening and can no longer login to Grommunio from Outlook 2019 (Grommunio Web login is working fine though), just keeps re-prompting for password. Running appliance from 12-22 that has been upgrade to SUSE 15.5 and been running without issue for several months. Last update prior to today was 03 October 2023 with no issues.
Have reset passwords from Grommunio Admin console, Web still works but no change to Outlook login. Have a second Grommunio instance that has not been updated with latest updates today and can still login to this instance from Outlook so issue is within on of the updates installed today.
Still investigating issue, will update if I find a cause, just posting in case others have had same issue and already have solution. Below is roughly the updates I installed tonight (taken from 2nd instance - but my two instances of Grommunio are normally updated several days apart not on the same day).
`Reading installed packages...
The following 59 packages are going to be upgraded:
aaa_base apparmor-abstractions apparmor-parser apparmor-parser-lang babeltrace
curl dracut dracut-mkinitrd-deprecated glibc glibc-extra glibc-lang
glibc-locale glibc-locale-base grommunio-admin-api grommunio-admin-web
grommunio-web gromox gromox-debuginfo gromox-debugsource grub2 grub2-i386-pc
grub2-i386-pc-extras grub2-x86_64-efi grub2-x86_64-efi-extras libapparmor1
libcurl4 libharfbuzz0 libHX32 libnghttp2-14 libolecf1 libopenssl1_1 libpff1
libsystemd0 libudev1 libX11-6 libX11-data libX11-xcb1 libXpm4 login_defs
mariadb mariadb-client mariadb-errormessages openssl-1_1 perl-Encode-IMAPUTF7
postfix postfix-mysql python3-rpm python3-urllib3 rpm shadow suse-module-tools
systemd systemd-coredump systemd-network systemd-rpm-macros systemd-sysvinit
udev xen-libs zypper
The following 92 NEW packages are going to be installed:
aaa_base-extras crda cups cups-client cups-config cups-filters dbus-1-x11
dmraid ghostscript ghostscript-x11 groff-full
grommunio-admin-api-bash-completion grub2-systemd-sleep-plugin gxditview
kernel-default-5.14.21-150500.55.31.1 kernel-default-extra
kernel-default-optional kernel-firmware-all kernel-firmware-amdgpu
kernel-firmware-ath10k kernel-firmware-ath11k kernel-firmware-atheros
kernel-firmware-bluetooth kernel-firmware-bnx2 kernel-firmware-brcm
kernel-firmware-chelsio kernel-firmware-dpaa2 kernel-firmware-i915
kernel-firmware-intel kernel-firmware-iwlwifi kernel-firmware-liquidio
kernel-firmware-marvell kernel-firmware-media kernel-firmware-mediatek
kernel-firmware-mellanox kernel-firmware-mwifiex kernel-firmware-network
kernel-firmware-nfp kernel-firmware-nvidia kernel-firmware-platform
kernel-firmware-prestera kernel-firmware-qcom kernel-firmware-qlogic
kernel-firmware-radeon kernel-firmware-realtek kernel-firmware-serial
kernel-firmware-sound kernel-firmware-ti kernel-firmware-ueagle
kernel-firmware-usb-network libavahi-client3 libavahi-common3 libavahi-glib1
libcups2 libcupscgi1 libcupsimage2 libcupsmime1 libcupsppdc1 libICE6
libidn2-devel libjasper4 liblcms2-2 libnetpbm11 libopenjp2-7 libpoppler126
libpoppler-cpp0 libqpdf26 libSM6 libtss2-esys0 libtss2-mu0 libtss2-rc0
libtss2-sys1 libXaw7 libXmu6 libXt6 lifecycle-data-openSUSE netpbm
openssh-askpass os-prober parallel-printer-support poppler-data poppler-tools
psutils python3-brotlipy python3-PySocks systemd-lang system-user-lp
wireless-regdb xbitmaps zypper-lifecycle-plugin zypper-log
zypper-needs-restarting
The following package requires a system reboot:
kernel-default-5.14.21-150500.55.31.1
59 packages to upgrade, 92 new.
Overall download size: 661.0 MiB. Already cached: 0 B. After the operation,
additional 677.5 MiB will be used.
Note: System reboot required.
`
If someone with better OpenSUSE skills than me can provide command to list what I installed tonight I can post that if it helps to further identify issue.
Found following errors in Monitoring logs that maybe relevant.
Gromox Http
[2023-10-21 17:48:24.608815]: ntlm_auth(stdout) EOF
Zcore Log
2023-10-21 17:32:46.283182]: Auth rejected for "user@domain.com": password error, please check it and retry
I have tested with all accounts in the upgraded instance and all accounts generate the same error.
Mark