My Oracle Support Banner

Replayformat Parameters Introduced in Convergence 3.0.1.4.0 Makes Login with Email Address Impossible (Doc ID 2378529.1)

Last updated on MARCH 25, 2019

Applies to:

Oracle Communications Convergence - Version 3.0.1 and later
Information in this document applies to any platform.

Symptoms

When upgrading Convergence to version 3.0.1.4.0, the only way to log in is by using the email address, when the left part of the email address is different than the UID. You can log into Webmail, but then Messaging Server, Calendar Server and Contact Server will try to find the account with a wrong email address given by Convergence. So with that issue, once the user is logged into Convergence, they receive popups telling them that there is some trouble with Messaging, Calendar and Contact servers.

If the UID is added as a way to connect "(|(uid=%U)(mail=%o))", there is no trouble because the services can find the account with the UID (which is good).

Scenario presented below:

A domain exists in the Directory Server (DS) <DOMAIN> (this is the default domain configured in Messaging Server). The inetDomainSearchFilter attribute is set to mail=%o in the domain's ldap entry.
A user exists with UID and email address in the domain.

The Messaging Server configuration parameter local.service.proxy.admin is set to "admin@<DOMAIN>".

When we log into Messaging Server using Thunderbird (IMAP) as <USERNAME@DOMAIN> --> everything works fine - login, folder listing, folder contents listing, mail send etc.

But when we attempt login to mshttpd the login fails.

From the DS access log:

 

Changes

Upgraded to Convergence 3.0.1.4.0.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.