--On Wednesday, March 27, 2024 1:07 AM + xpzhang1...@gmail.com wrote:
I did ldapsearch to export schema from source ldap server, cmd is:
ldapsearch -x -LLL -H "ldap://xxx:389; -D
"cn=admin,ou=AdminUsers,dc=example,dc=com" -W -b "cn=schema" -o
ldif-wrap=no > source-schema.ldif
but
I did ldapsearch to export schema from source ldap server, cmd is:
ldapsearch -x -LLL -H "ldap://xxx:389; -D
"cn=admin,ou=AdminUsers,dc=example,dc=com" -W -b "cn=schema" -o ldif-wrap=no >
source-schema.ldif
but ldapadd this ldif to target server still report:
[root@phx-ldap-ol8 openldap]#
--On Tuesday, March 26, 2024 11:57 PM + xpzhang1...@gmail.com wrote:
I gave a try like this way:
I installed an openldap 2.6 as target server, started it up with initial
slapd.ldif. Then I tried to ldapadd entries that exported from source
server, but failed on the first entry, error
I gave a try like this way:
I installed an openldap 2.6 as target server, started it up with initial
slapd.ldif.
Then I tried to ldapadd entries that exported from source server, but failed on
the first entry, error message:
[root@ldap-ol8 openldap]# ldapadd -H ldap:/// -D
On 2024-03-25 10:42, xpzhang1...@gmail.com wrote:
Tech Folks, thanks for your replies.
There are too many unknowns for anyone to give you much help in creating
a new LDAP instance. What OS? What version of OpenLDAP? Do you have
full access to the directory data using LDAP, i.e. what
--On Monday, March 25, 2024 6:42 PM + xpzhang1...@gmail.com wrote:
Tech Folks, thanks for your replies.
In real world, we often face such tasks to take over a thing that not
belong to you, and you even only have limited access to that thing.
Is there a way figuring out configuration,
Tech Folks, thanks for your replies.
In real world, we often face such tasks to take over a thing that not belong to
you, and you even only have limited access to that thing.
Is there a way figuring out configuration, schema, and etc from ldif files
generated by ldapsearch from source server?
In several organizations where I worked without root access, I requested sudo
permissions for slapcat.
But to not have a shell, that makes life more difficult. Maybe you could get
root to set up a cron to dump the extract using slapcat and deliver it somehow.
Chris Paul |
--On Monday, March 25, 2024 4:51 PM + xpzhang1...@gmail.com wrote:
Because port 22 is not open, I can't ssh or rlogin to the server. only
can run ldapsearch such client commands. nmap to the server only see
port 389 and 636 open. I don't know how the server owner maintain,
startup/stop
This is sounding pretty shady. It sounds like it isn’t your data.
From: xpzhang1...@gmail.com
Sent: Monday, March 25, 2024 11:51 AM
To: openldap-technical@openldap.org
Subject: RE: [EXTERNAL] how to migrate an openldap server to a new linux server
Because port 22 is not open, I can't ssh
Because port 22 is not open, I can't ssh or rlogin to the server. only can run
ldapsearch such client commands.
nmap to the server only see port 389 and 636 open. I don't know how the server
owner maintain, startup/stop the server.
Why is it not accessible? It sounds like that is the 1st problem you need to
solve. You can add an ldapi to the startup.
From: xpzhang1...@gmail.com
Sent: Saturday, March 23, 2024 3:34 PM
To: openldap-technical@openldap.org
Subject: RE: [EXTERNAL] how to migrate an openldap server to a new
the problem here is that source openldap server only have port 389 opened, it
is not accessible, not able to run slapcat.
I would backup the database from the old server and restore it to the new one.
Old Server
{PATH}openldap/sbin/slapcat -n 0 – {PATH}/openldap/etc/openldap/slapd.d -l
{PATH}/slapd.d.ldif
{PATH}openldap/sbin/slapcat -b {BASE DN} -F
{PATH}/openldap/etc/openldap/slapd.d -l {PATH}/config.ldif
Copy
14 matches
Mail list logo
