[LDAP] can't create new authentication mode

Added by Petr Vosa over 1 year ago

Hello,

iam trying to link redmine with my Active Directory server.

Following the guide ([[http://www.redmine.org/projects/redmine/wiki/RedmineLDAP]]) i filled the form.
But when i try to Create it, i get this error:

Internal error
An error occurred on the page you were trying to access.
If you continue to experience problems please contact your Redmine administrator for assistance.

If you are the Redmine administrator, check your log files for details about the error.


And the log says this (some data replaced with x):

Started POST "/redmine/auth_sources" for xxx
Processing by AuthSourcesController#create as HTML
Parameters: {"utf8"=>"✓", "-xxxxxxxxxxxxx-"}, "commit"=>"Create"}
Current user: xxx (id=-xx-)
Completed 500 Internal Server Error in 44ms (ActiveRecord: 5.3ms)

NoMethodError (undefined method `verify_peer=' for #<AuthSourceLdap:0x00557d35bf8f08>):

app/models/auth_source_ldap.rb:133:in `ldap_mode='
lib/redmine/safe_attributes.rb:88:in `safe_attributes='
app/controllers/auth_sources_controller.rb:96:in `build_new_auth_source'
lib/redmine/sudo_mode.rb:63:in `sudo_mode'


I have connectivity to my LDAP server.
I tried many different variations when filling the form, in case i typed in something incorrectly, but still getting the same error.
What could be causing this error, please?

Replies (3)

RE: [LDAP] can't create new authentication mode - Added by Thomas Malkus 4 months ago

Hi!

Got absolutly the same error with Redmine 4.1.0 on Debian 10.2.

I have connectivity to my LDAP server.

I've checked connectivity to DC, DNS is also ok.

Tom

RE: [LDAP] can't create new authentication mode - Added by Go MAEDA 4 months ago

Did you run "bin/rake db:migrate RAILS_ENV=production" after upgrading Redmine?

Probably you are using Redmine 4.0.0 or later against the database for an older version of Redmine. See RedmineUpgrade for details.

RE: [LDAP] can't create new authentication mode - Added by Thomas Malkus 4 months ago

Yes, sure ;-) I had made an update from version 4.0.5 to 4.1.0 in the hope that this problem was already solved.

(1-3/3)