Does Authcachettl Control Anything Other Than Authentication?
(Doc ID 2730560.1)
Last updated on NOVEMBER 22, 2020
Applies to:Oracle Communications Messaging Server - Version 8.0.2 and later
Information in this document applies to any platform.
Does authcachettl control anything other than authentication?
On the MMPs, imapproxy.replaypass = 0 is used and specify imapproxy.storeadmin and storeadminpass.
This is also used for webmail (and POP is not being used).
Due to this, IMAP authentication on the backends is using the storeadmin userid, not the actual user uids. The users are only really authenticated on the frontends.
Historically, authcachettl had been set to 0, so password changes and user lock-outs take effect immediately.
Since IMAP auth on the backends is only really doing auth of the storeadmin proxy userid, the load of BIND requests could be reduced by enabling the authcache on the backends.
Does authcachettl control anything other than authentication (like mailHost or mailUserStatus) on the backend? In other words, in the imapd process on the backend, what attributes are controlled by authcachettl?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!