In root, yes. But no success at all, not even as suffix.
When creating a suffix, IDSWebApp returns 'OK', but it doesn't appear.
Not even when I add it to the suffixes list in the ISVD server config YAML.
I wonder how they managed to create the entry in the root.
Michael
Original Message:
Sent: Fri August 29, 2025 07:21 AM
From: Mita Mitic
Subject: Is there a way to migrate secAuthority=Default from SDS to ISVD?
I see. Not sure why it will not work.
Let me check this:
Adding suffixes in not the same as adding entries. In IDSWebApp, you go Server Administration -> Manage Server Properties, then Tab "Suffixes". There from, you add a suffix.
There is no other place where you can create suffix, but in a root.
Is it the place where you are trying to add it?
Sorry if this is already tried.
What is the error when you try_
Thanks,
Mita
------------------------------
Mita Mitic
Original Message:
Sent: Fri August 29, 2025 06:45 AM
From: Michael Kochenburger
Subject: Is there a way to migrate secAuthority=Default from SDS to ISVD?
Hi Mita,
thanks, but this doesn't work. Btw. idsxcfg needs Java, and there is no Java in the container.
But I can use the IDSWebApp over the browser.
However, with the same problem, secAuthority=Default cannot be created in the root.
Michael
------------------------------
Michael Kochenburger
Original Message:
Sent: Fri August 29, 2025 06:05 AM
From: Mita Mitic
Subject: Is there a way to migrate secAuthority=Default from SDS to ISVD?
Hi Michael,
I believe you need to create suffix secAuthority=Default on ISVD instance first
You may do it with graphic tool of ISVD, idsxcfg (it is in a sbin folder of the installation)
Hope this helps,
Mita
------------------------------
Mita Mitic
Original Message:
Sent: Fri August 29, 2025 05:52 AM
From: Michael Kochenburger
Subject: Is there a way to migrate secAuthority=Default from SDS to ISVD?
Hello,
I have to migrate the data from a SDS Virtual Appliance 8.0.1 LDAP to a ISVD 10.0.3 LDAP container.
In SDS is a root entry SECAUTHORITY=DEFAULT, that I cannot migrate. It must have been created by the Access Manager.
DIT
> Root DSE
> (..other suffixes..)
> SECAUTHORITY=DEFAULT
The LDIF Import throws an error, when it comes to 'dn: secAuthority=Default', because a parent entry is required.
But secAuthority=Default should not have a parent.
The manual creation of this DN in the root with Apache for example is also not possible.
------------------------------
Michael Kochenburger
------------------------------