[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: LDAP and oracle

To: florian.engelmann@bt.com
Subject: Re: LDAP and oracle
From: "Andris Eiduks" <aeiduks@gmail.com>
Date: Wed, 16 Jan 2008 10:49:06 +0200
Cc: openldap-technical@openldap.org
In-reply-to: <A894B5EAD9255144AFFB5CD7C31E2A6901979344@E03MVC4-UKBR.domain1.systemhost.net>
References: <A894B5EAD9255144AFFB5CD7C31E2A69018A2310@E03MVC4-UKBR.domain1.systemhost.net> <79a0106f0801152319u2f786f8dwd6e0ded62ecf5199@mail.gmail.com> <A894B5EAD9255144AFFB5CD7C31E2A6901979344@E03MVC4-UKBR.domain1.systemhost.net>

Hi,

thank you for your answer. I was toled by the project leader of our LDAP migration that the LDAP clients are caching the authentication information and users like the oracle user or apache won't create new sessions for every operation. I also was toled that the clients cache those information for 12 hours so we will never have any hanging oracle databases due to a crash of our LDAP servers. Is that true?

Hi!

I'm not sure.

And new Oracle session creation (or not ) for every new operation (and necessary new user authentication) depends from your solution.
How did You set up this authentication?
I think that Oracle doesn't cache user password or data .

References:
- LDAP and oracle
  - From: <florian.engelmann@bt.com>
- Re: LDAP and oracle
  - From: "Andris Eiduks" <aeiduks@gmail.com>
- AW: LDAP and oracle
  - From: <florian.engelmann@bt.com>

Prev by Date: AW: LDAP and oracle
Next by Date: Re: sles 10 synchronize 2 ldapservers
Index(es):
- Chronological
- Thread