You can change the username of each of the users in the database to match
their usernames in LDAP. You'll then need to set each to use an "unusable"
password, which unfortunately cannot be done through the administration UI.
You can do this through the management shell by doing:
$ rb-site manage /path/to/sitedir shell
from django.contrib.auth.models import User
for user in User.objects.filter(is_superuser=False):
That will disable the in-database hashed password for each non-admin user
(you always want at least your primary admin user to have an in-database
password, in case LDAP goes down or there's a configuration issue).
How many users do you have in the database? There are ways to automate the
renaming of the users if needed.
On Thu, Aug 9, 2018 at 7:27 PM <mojgan.samifa...@gmail.com> wrote:
> We are currently using standard authentication but I have set up new
> server to use LDAP authentication. Is there a way that I can map the
> Standard ID to LDAP id after I move the database content to new server
> Supercharge your Review Board with Power Pack:
> Want us to host Review Board for you? Check out RBCommons:
> Happy user? Let us know! https://www.reviewboard.org/users/
> You received this message because you are subscribed to the Google Groups
> "Review Board Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to reviewboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
President/CEO of Beanbag <https://www.beanbaginc.com/>
Makers of Review Board <https://www.reviewboard.org/>
Supercharge your Review Board with Power Pack:
Want us to host Review Board for you? Check out RBCommons:
Happy user? Let us know! https://www.reviewboard.org/users/
You received this message because you are subscribed to the Google Groups
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.