Unexpected User Authentication Replay Behavior From MMP To Store
(Doc ID 2257354.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Communications Messaging Server - Version 7.0.5 and later
Information in this document applies to any platform.
Unexpected user authentication replay behavior from MMP to store.
The following is configured on the MMP in PopProxyAService.cfg and ImapProxyAService.cfg:
Given the replay config on the MMP, the expectation is that the uid@domain, as derived from LDAP, is replayed to the store. Instead, it appears that the UID is whatever the client inserted as the UID. As a result in the above configuration, users cannot specify a mailAlternateAddress in their IMAP or POP3 client when connecting the MMP to access their mailbox.
Is this the expected behavior? If it is, what is the best solution to permit IMAP/POP3 authentication where the username in the client is a mailAlternateAddress value?
For example, should sasl.default.ldap.searchfilter on the backend always be the same as the MMP?
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