Project

General

Profile

Actions

Bug #4006

closed

Social auth settings are not encypted

Added by Marcin Kuzminski [CTO] almost 8 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
High
Category:
-
Target version:
Start date:
09.06.2016
Due date:
% Done:

0%

Estimated time:
Sorting:
Commit Number:
Affected Version:

Description

Start with empty database, enable social auth like bitbucket.

Check inside database, to find the things are not encrypted:

rhodecode=# select * from rhodecode_settings where app_settings_name ILIKE 'auth_bitbucket%';
 app_settings_id |       app_settings_name        |        app_settings_value        | app_settings_type
-----------------+--------------------------------+----------------------------------+-------------------
             131 | auth_bitbucket_consumer_key    | *****               | unicode
             132 | auth_bitbucket_enabled         | True                             | bool
             133 | auth_bitbucket_consumer_secret | **** | unicode
             134 | auth_bitbucket_cache_ttl       | 0                                | int
(4 rows)
Actions #1

Updated by Johannes Bornhold almost 8 years ago

  • Status changed from New to In Progress
Actions #2

Updated by Johannes Bornhold almost 8 years ago

  • Status changed from In Progress to Resolved
Actions #3

Updated by Marcin Kuzminski [CTO] almost 8 years ago

  • Status changed from Resolved to Closed

confirmed things works as expected, saving settings encrypts values now.

Actions

Also available in: Atom PDF