This article is possibly outdated. It mentions an older version of a software or tool. I haven't checked if the links are still working!
IBM sold their collaboration tools portfolio to HCL Software in 2019, so the product names changed and most of the IBM links are no longer working.
Today IBM released CR1 on IBM Fixcentral. CR1 is a set of 17 cumulative fixes and enable Mobile Admin (didn’t verified this, hope it will be there) too.
Links for all CR1 Downloads (Multi OS Fixes)
Fix list for IBM Connections 4.0 CR1 – Very long, seems to fix a lot
IBM Connections 4.0 CR1 Post-install Deployment Configuration Steps
Update strategy for IBM Connections 4.0
Cross-product relationship information
You have to download 18 packages, because a new update installer is mandatory!
A lot of people don’t like to store credentials in mobile apps or browsers. A good workaround is the usage of OAuth 2.0 tokens, but the application needs to support it and the server you’re talking to too. The IBM Connections Mobile App can use it for authentication.
OAauth2 can be used directly with WebSphere Application Server and Connections 6.0. There are no special OAuth servers or applications needed!
The Documentation at IBM was a little bit confusing for me, there are lots of sidenotes, but you just need to do following steps, to use OAuth 2.0 token-based authentication with the IBM Connections Mobile App.
Within the fixlist of the new released CR3 of IBM Connections 5 there are several new configuration options mentioned. One of the interesting ones for me is the mobile update parameter AllowRemoveAccount. The default value is “false” and your Connections environment still works before, but what’s changed when you set this to true?
The official documentation is already uptodate and shows us:
When you set this option to true, accounts can be removed from a mobile device without requiring the user to login and without any authorization check. The user is asked to confirm the deletion of an account before it is removed.