[OPENAM-11763] "Saving" CTS configuration overwrites the bind password Created: 15/Sep/17  Updated: 05/Oct/17  Resolved: 05/Oct/17

Status: Closed
Project: OpenAM
Component/s: XUI
Affects Version/s: 13.5.1, 14.1.1, 14.5.0
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: John Noble Assignee: Julian Kigwana [X] (Inactive)
Resolution: Duplicate Votes: 5
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux


Attachments: PNG File CTSScreenShot.png     File openam.example.com.har    
Issue Links:
Depends
depends on OPENAM-11834 Passwords being set to empty strings ... Closed
Duplicate
duplicates OPENAM-11834 Passwords being set to empty strings ... Closed
Regression
Relates
relates to OPENAM-10382 If we set up External CTS wrongly the... Closed
relates to OPENAM-10383 Validation of External CTS store usin... Open
relates to OPENAM-11116 Admin console should still be accessi... Closed
Target Version/s:
Sprint: AM Sustaining Sprint 42, AM Sustaining Sprint 43
Story Points: 1
Support Ticket IDs:

 Description   

Bug description

Saving changes on "CTS Token Store" tab clears saved bind password. Password field is on "External Store Configuration" tab.

Password field is 'blanked' when config is viewed, but this is not in any way obvious when saving changes on another tab.

How to reproduce the issue:

  1. Set up AM and working external CTS configuration
  2. Via admin console: Configure->Server Defaults-> CTS
  3. On the 'CTS Token Store' tab, click 'Save Changes'
  4. Restart OpenAM

The result is AM server cannot create a connection to CTS on reboot, it will not be able to create any sessions, including for admin console access.

Expected Behaviour

CTS bind Password should not be overwritten

Saving the contents of one tab should not affect another

Work around

CTS bind password must be re-entered when saving any changes to CTS configuration in the admin console.

  



 Comments   
Comment by Julian Kigwana [X] (Inactive) [ 21/Sep/17 ]

Could this be a well disguised duplicate of OPENAM-11705?

Comment by Julian Kigwana [X] (Inactive) [ 05/Oct/17 ]

This bug is a symptom of OPENAM-11834

Generated at Sun Sep 27 07:50:45 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.