Done and done, although imported users' membership in their OpenLDAP
primary group wasn't preserved because a al catch22, that group could be
made default until it was imported, but was easily rectified via the UI
I can almost live with these gigantic UIDs set for new users but the
default
That's terrific, Rob - thanks very much. Users and Groups import
smoothly with a little additional tweaking
ipa -v migrate-ds --with-compat
--bind-dn="cn=Manager,dc=ldapdomain,dc=local"
--user-container="ou=People,dc=blue-bolt,dc=local"
--group-container="ou=Group,dc=ldapdomain,dc=local"
On 11/04/2015 04:11 PM, Cal Sawyer wrote:
> That's terrific, Rob - thanks very much. Users and Groups import smoothly
> with
> a little additional tweaking
>
> ipa -v migrate-ds --with-compat --bind-dn="cn=Manager,dc=ldapdomain,dc=local"
> --user-container="ou=People,dc=blue-bolt,dc=local"
>
Hi
Very new to IPA and setting up a proof of concept system that i hope
will replace my existing OpenLDAP 2.3 (no SASL) setup. I'm trying to
import People, Group ou's into IPA using "ipa migrate-ds". The IPA and
existing LDAP directories have different BaseDNs (eg ipadomain.local on
IPA,
Cal Sawyer wrote:
> Hi
>
> Very new to IPA and setting up a proof of concept system that i hope
> will replace my existing OpenLDAP 2.3 (no SASL) setup. I'm trying to
> import People, Group ou's into IPA using "ipa migrate-ds". The IPA and
> existing LDAP directories have different BaseDNs (eg
Cal Sawyer wrote:
> That's terrific, Rob - thanks very much. Users and Groups import
> smoothly with a little additional tweaking
>
> ipa -v migrate-ds --with-compat
> --bind-dn="cn=Manager,dc=ldapdomain,dc=local"
> --user-container="ou=People,dc=blue-bolt,dc=local"
>
