-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Joining multiple NS7 systems with the same account provider to NS8 fails #7111
Labels
verified
All test cases were verified successfully
Comments
DavidePrincipi
added a commit
to NethServer/nethserver-ns8-migration
that referenced
this issue
Nov 13, 2024
The LDAP DN syntax is case insensitive. When the BaseDN values are compared we must ignore their case. Refs NethServer/dev#7111
in
|
DavidePrincipi
added
the
testing
Packages are available from testing repositories
label
Nov 13, 2024
Amygos
added
testing
Packages are available from testing repositories
and removed
testing
Packages are available from testing repositories
labels
Nov 13, 2024
tested: VERIFIED |
nrauso
added
verified
All test cases were verified successfully
and removed
testing
Packages are available from testing repositories
labels
Nov 13, 2024
in
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In some NS7-to-NS8 migration scenarios, you may have multiple NS7 systems (e.g., NS7_1, NS7_2, and NS7_3) that share the same account provider.
For instance, NS7_1 might have Active Directory onboard, with NS7_2 and NS7_3 joined to NS7_1 to access the same user base.
In such cases, you should be able to migrate all services to NS8, joining NS7_1, NS7_2, and NS7_3 to NS8 simultaneously.
However, after joining NS7_1 (the first NS7 that needs to be joined), attempts to join the other NS7 systems fail.
Steps to reproduce
Expected behavior
Both NS7 systems should join NS8 successfully
Actual behavior
The second NS7 fails to join NS8, displaying an error related to the external user domain.:
Components
NS8:
NS7:
The text was updated successfully, but these errors were encountered: