Hi Pierre Rogier,
I've tried to follow this document for pass through authentication
https://access.redhat.com/documentation/en-us/red_hat_directory_server/11/html/administration_guide/configuring_directory_databases-creating_and_maintaining_database_links
For that i've create two 389ds ldap
Hi Willam Brown,
I've tried to follow this document for pass through authentication
https://access.redhat.com/documentation/en-us/red_hat_directory_server/11/html/administration_guide/using_the_pass_through_authentication_plug_in
For that i've create two 389ds ldap servers
i've created ldap1
Hi Willam,
I couldn't find any documentation for pam-passthru authentication.
Can you please share any documentation related how to achieve pam-passthru and
how to do verification for the same
Regards
Nitesh
___
389-users mailing list --
Apologies for creating confusion.
My Problem statement:
I've a Server1 on which I've installed 389ds lets call it out as internal_ldap.
I've installed Openstack on the same server and I'm integrating this
internal_ldap as my ldap backend to Openstack
On Wed, May 4, 2022 at 2:05 PM parimala nitesh
wrote:
> Hi Pierri,
>
> Thank you Pierri for the response.
> My queries are inline
>
> [1]If you can set up replication between the two LDAP server instances
> then the data will be available on both instances.
>
> What if the users are getting
Yes Willam, I'm expecting something like that. After integration, if some users
are getting added on external_ldap they should also get authenticated on 389ds
note: external ldap can be 389ds or openldap or windows AD
Regards
Parimala Nitesh
___
Hi Pierri,
Thank you Pierri for the response.
My queries are inline
[1]If you can set up replication between the two LDAP server instances
then the data will be available on both instances.
What if the users are getting added on external LDAP. Then i've to replicate it
again?
[2]If server2
Hi Parimala,
Welcome to 389ds.
Several ideas came to mind:
[1] If you can set up replication between the two LDAP server instances
then the data will be available on both instances.
[2] If server2 suffix is different from server1 suffix, then you could use
chaining.
(so that request to
