Fix SSO Bug/Hashed Passwords

CHANGELOG.md

@@ -4,6 +4,11 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 
 ---
 
+## [1.11.0-bb.3]
+## Fixed
+- Fixed an SSO bug caused by hashed passwords not being set consistently - BB Issue #135
+
+
 ## [1.11.0-bb.2]
 ## Changed
 - Modified chart to handle monitoring more cleanly

chart/Chart.yaml

 apiVersion: v2
 name: anchore-engine
-version: 1.11.0-bb.2
+version: 1.11.0-bb.3
 appVersion: 0.9.0
 description: Anchore container analysis and policy evaluation engine service
 keywords:

chart/templates/bigbang/sso/configure-sso.yaml

@@ -11,8 +11,8 @@ spec:
       annotations:
         sidecar.istio.io/inject: 'false'
     spec:
-      # imagePullSecrets:
-      # - name: repo1-registry-read-creds
+      imagePullSecrets:
+        - name: {{ .Values.anchoreEnterpriseGlobal.imagePullSecretName }}
       containers:
         - name: configure-sso
           image: {{ .Values.anchoreEnterpriseGlobal.image }}

chart/values.yaml

@@ -226,13 +226,13 @@ anchoreGlobal:
     privateKeyName: Null
     publicKeyName: Null
 
-  oauthEnabled: false
+  oauthEnabled: true
   oauthTokenExpirationSeconds: 3600
 
   # Set this to True to enable storing user passwords only as secure hashes in the db. This can dramatically increase CPU usage if you
   # don't also use oauth and tokens for internal communications (which requires keys/secret to be configured as well)
   # WARNING: you should not change this after a system has been initialized as it may cause a mismatch in existing passwords
-  hashedPasswords: false
+  hashedPasswords: true
 
   # Configure the database connection within anchore-engine & enterprise-ui. This may get split into 2 different configurations based on service utilized.
   dbConfig: