Essbase 9.3.1 under SS 9.2 - why it did not stop authenticting?

We installed a new Essbase server, and because it was x64, we had to install 9.3.1 version. The rest of installation, including Shared Services, is 9.2.0.2. It is temporary untill full upgrade, but for business reasons we cannot upgrade at this point. And yes, I know that it is not a supported configuration, but it works for what we need.
Shared Services are configured for extrnal authentication using OpenLdap.
Essbase x64 9.3.1 server runs in native mode, but authenticates users externally, so we are happy.
Here is the situation. The AD account that is used by OpenLdap was accidentally disabled. Immediately AAS and old (x32 9.2.0.2) Essbase servers stopped authenticating users, as expected.
The new 9.3.1 server continued to work just fine! Looks like for existing users, authentication info was cached somewhere. Any ideas? If it is indeed cached, how often is it refreshed, and is it forced to be refreshed by essbase service restart.
For security reasons, I would like to know the cause.

I've seen issues like this when the time on the server running HSS and the time on the server running Essbase is out of sync.
Check that both times are in sync and then restart the services and try registering.
Cheers,
Gee

Similar Messages

Maybe you are looking for