ERROR 24-05-2022 10:08:05 [MailClient] -- Exception while processing mailbox recordersbm@o365.MyCompany.com : IX4 BAD User is authenticated but not connected .
nested exception is: com.sun.mail.iap.BadCommandException: R4 BAD User is authenticated but not connected . at com.sun.mail.imap.IMAPFolder.logoutAndThrow(IMAPFolder.java:1180)
This authentication choice is good for users who are internal to an organization and are logged into a domain. However, this is not suitable choice if you plan to need to allow other users access (e.g. outside of the domain). To get around this, you will need to make your server accessible to those users outside of your organization, (you can alternatively set up a second server outside a firewall that connects to the same production database.)
You will see these errors if you have enabled "Client Certificate Authentication" from within Configurator but have not followed the steps yet to configure Composer to use those settings. If you look in Configurator and go to the Security > Client Certificate Authentication tab and the "Enable SSL Client Certificate Authentication" checkbox is checked then make sure you also do the following for your Composer users . Open the SBM Installation Guide for your version of SBM
Users are able to log into the SBM Application Engine ( http://servername/tmtrack/tmtrack.dll ?), however, no one can log into the Repository ( http://servernmae/mashupmgr ) or connect using Composer. Composer gives error: Connection attempt failed.