Showing posts with label Windows Authentication. Show all posts
Showing posts with label Windows Authentication. Show all posts

Saturday, June 13, 2015

IM Server fixes autorization of Android clients if Windows Authentication is enabled

We released a priority update for the communication server that fixed problem with accepting the Android clients if Windows Authentication is enabled for user accounts. It seems that the IM server had a bug that did not allow to connect from Android devices under the same account name used by a user in desktop messenger. We strongly recommend to update an existing server software to version 4.3.17 to avoid this issue.

Download Bopup Communication Server version 4.3.17 — Enterprise-level IM & Chat software for offices

Wednesday, April 29, 2015

Log out function is available in IM clients even Simple or Windows Authentication are used

Both Bopup Messenger and Bopup Observer messaging clients improved "Log out..." function that is accessible from Messages menu. Now that item is available always when a messenger is connected and even Simple or Windows Authentication modes are used. Previously this menu option was available only if Private login/password authentication used.

Now it is possible to disconnect from the IM server without closing the messenger application. This will allow to change login name and enter to IM network with another credentials.

Another important change is that the messaging clients will bring and show "Login" pane in the main window every time when the same user has entered to the IM network from another computer/device and when only a single connection per each account is permitted. Now the pane will be shown not only if Private login/password used but also under Simple and Windows Authentication.

Download Bopup Messenger version 6.5.4 and Bopup Observer version 5.5.3

Monday, February 23, 2015

Useful update of the communication server software

We released Bopup Communication Server version 4.3.11 that comes with useful improvements and updates. It also solves the issue explained in the recent post when Android app is unable to connect if Windows Authentication is used for the user account. See detailed information on changes in this version below.

What's new:

Added function to set a password for a user manually if Private login/password authentication is used
The server console added an option to set a password for the account if third-party authentication is used. That's too useful addition because our customers asked about this function for a long time. So now it is possible to change password for the account manually through account properties window and not only to reset it in order to force the user to create a new one by himself.

Added ability to use same IM account name on Android messenger app even if Windows Authentication is enabled
Another important change is about support of the messenger application for Android platform. Prior versions of the IM server required to have different accounts for the same user if the software works on Windows domain network. Or change the authentication for that user to Private login/password mode. The latest version of the server now supports using the same IM account on different devices, and use Windows Authentication on desktop messenger and Private login/password for Android app.

Fixed issues with checking new updates
We were reported that the console did not check for updates correctly and even brought a connection error message. That forced us to discover several issues and one was in our website since May 2014! Now everything works as it should and properly.

Download Bopup Communication Server version 4.3.11

Friday, February 20, 2015

Known issue: Android app does not support Windows Authentication

Here is an issue with authentication used by our IM client for mobile platform called Bopup Messenger for Android. It does not support Windows Authentication so the application cannot accept domain name, account and password to connect to communication server and brings an SSPI authorization error. The problem is in SSPI mechanism used by our IM server and which is not supported by Android platform because it's implementation is available for Windows system only. We will try to work out this issue in future versions of the software, stay updated.