Project

General

Profile

Actions

Defect #44213

closed

table: auth_sources password

Added by Sheng Ze Fan 3 days ago. Updated 2 days ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
LDAP
Target version:
-
Resolution:
Duplicate
Affected version:

Description

Dear Support:

Table name: auth_sources
Field name: account_password
not encrypt, how to encrypt?

thanks


Related issues

Is duplicate of Redmine - Feature #7411: Option to cipher LDAP ans SCM passwords stored in the databaseClosed2011-01-22Actions
Actions #1

Updated by Holger Just 2 days ago

  • Is duplicate of Feature #7411: Option to cipher LDAP ans SCM passwords stored in the database added
Actions #2

Updated by Holger Just 2 days ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

You can set an encryption password with the database_cipher_key key in your config/configuration.yml file. After setting this key, you can encrypt existing passwords in your database with this key by running `rake db:encrypt RAILS_ENV=production`.

See the commented example in config/configuration.yml.example:

# Key used to encrypt sensitive data in the database (SCM passwords,
# LDAP passwords, and TOTP (two-factor authentication) secret keys).
# If you don't want to enable data encryption, just leave it blank.
# WARNING: losing/changing this key will make encrypted data unreadable.
#
# If you want to encrypt existing data in your database:
# * set the cipher key here in your configuration file
# * encrypt data using 'rake db:encrypt RAILS_ENV=production'
#
# If you have encrypted data and want to change this key, you have to:
# * decrypt data using 'rake db:decrypt RAILS_ENV=production' first
# * change the cipher key here in your configuration file
# * encrypt data using 'rake db:encrypt RAILS_ENV=production'
Actions

Also available in: Atom PDF