I don't see that particular file/path, but I did edit this file (/var instead of /opt):

/var/www/iredadmin/settings.py (I'm guessing that is the one you are referring to)

##############################################################################
# Place your custom settings below, you can override all settings in this file
# and libs/default_settings.py here.
#
DEFAULT_PASSWORD_SCHEME = 'SSHA+SSHA512'

That seems to do the trick, but I have a couple of questions.

When the password is updated in iRedAdmin-Pro, it is always the first userPassword that gets updated, leaving the second one (and third, etc) that I added manually untouched - correct?

Because the settings.py is in the symlinked folder to the designated version directory, changes to that file will not survive an upgrade, correct?

Thanks.
Jeff

Thanks, and just to be clear, the upgrade process copies the settings.py file from the current version directory to the new version directory? The reason I ask is that the settings.py is physically in the iRedAdmin-Pro-LDAP-3.5 directory which is a symlinked directory:
lrwxrwxrwx  1 root      root        22 Mar 28 08:14 iredadmin -> iRedAdmin-Pro-LDAP-3.5

As to the multiple passwords, I have tested with a couple of accounts by manually adding a new userPassword field, and when I updated the password for that user in the iRedAdmin-Pro interface there is still only one password entry and confirmation on that page. The user's original password is updated, and the second one that I created manually is untouched (which is good). Should I be seeing the multiple password fields now in the iRedAdmin-Pro password change page?

I think perhaps I didn't make myself clear in what I needed.

I have a user account, testuser@domain.com
I assigned a password - "password1" - through the iRedAdmin dashboard.

Using an LDAP administration tool, (or using a ldif file) to add an attribute, I created a second password - "password2" so there are now two instances of userPassword each with a different value.

This is required because I am also going to be using the LDAP server for Radius authentication and provisioning which requires a second and distinct password for the same user, hence the "password2" entry.

I thought it had worked in testing after making the change you suggested, but I was testing against the wrong LDAP server.

It looks like what is happening is that iRedAdmin is updating both userPassword entries when I modify the password through the dashboard with the same password with different hashes.

What I need is for the Password change in the dashboard to only update the first entry and leave the second one alone. I require two completely different passwords for the same user.

Ideally, I would see both passwords on the dashboard page to allow editing them both separately, but I know that is not likely to happen, I can make any of those changes manually.

And one more question: When I make changes in the settings.py file, what all do I need to restart in order for the changes to take effect?

Thanks!

The reason for two passwords is that we need users to have two passwords, one for email, one of their PPPOE login through Radius.
Email passwords get changed regularly, but PPPOE passwords, which are usually stored in the user's router does not. If the email password is changed and the PPPOE password is updated to the new password, same as the email, then the user is denied access to connect to the internet, leading to support calls trying to help people log into their router and change the the broadband password.

As far as knowing which one, could it not be done the same way as other multi-value attributes, such as title, telephone number etc? Or would there be a way of only updating the first entry, and not touching any others?

As I indicated, I know this is not something that would appeal to, or be needed by most other users, but if you could point me in the right direction that would be helpful. Not being able to use multiple passwords is the only thing preventing me from integrating Radius into my LDAP server.

Thanks.
Jeff