[OPENAM-13578] KBA are not updatable after upgrade Created: 17/Sep/18  Updated: 19/Jul/19  Resolved: 27/Sep/18

Status: Resolved
Project: OpenAM
Component/s: self-service
Affects Version/s: 6.0.0,, 5.5.2
Fix Version/s:, 6.5.0, 6.0.1, 5.5.2

Type: Bug Priority: Major
Reporter: Ľubomír Mlích Assignee: Adam Heath
Resolution: Fixed Votes: 0
Labels: EDISON
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive debug-1.zip     PNG File screen.png    
Target Version/s:
Rank: 1|hzpuen:
Sprint: AM Sustaining Sprint 55
Story Points: 5
Needs backport:
QA Assignee: Filip Kubáň [X] (Inactive)
Verified Version/s:
Needs QA verification:
Functional tests:
Are the reproduction steps defined?:
Yes and I used the same an in the description


Bug description

User can't change his answers to security questions after AM upgrade from 5.5.1 to 5.5.2. It is automatically tested by com.forgerock.openam.functionaltest.restcommon.user.selfservice.TestUssKbas.Setting KBAs for a user when the realm user sets their KBA answers when the update succeeds when the update is done using REST "beforeEach" hook

How to reproduce the issue

  1. install AM 5.5.1
  2. upgrade to AM 5.5.2
  3. add self service
  4. enable forgotten password and security questions
  5. login as demo user
  6. try to add security question
Expected behaviour
question is added
Current behaviour
There is error, see screen. See debug


Comment by Adam Heath [ 25/Sep/18 ]

PATCH-1420 contains a similar response being observed when trying to patch the related JIRAs for a customer  (OPENAM-11961 OPENAM-11989) - perhaps there is an upgrade step missing here related to the additional steps that had to be carried out here by Lawrence in that patch


Comment by Adam Heath [ 25/Sep/18 ]

Initally noticed that the following commit was missing from the 5.5.x branch and thought that this may be it - https://stash.forgerock.org/projects/OPENAM/repos/openam/pull-requests/3665/commits/e0b5d18fd692dbf0ba1bb1aac7a5b24b57d45483 

However, have included that update and can still see the issue when running the tests manually or when running the tests via temper : 

temper functional-tests --deploy 13.5.2 --upgrade-to 5.5.3-SNAPSHOT --hostname am.localtest.me --container tomcat7 --only-classes TestUssKbas

EDIT: Noted that the sustainign/5.5.x PR explicitly states that this is not needed - so ignore this comment.

Comment by Filip Kubáň [X] (Inactive) [ 12/Oct/18 ]

verified on ForgeRock Access Management Build 70748811ef (2018-October-12 05:22)

security questions can be modified after upgrade

Comment by Filip Kubáň [X] (Inactive) [ 19/Jul/19 ]

Verified on: ForgeRock Access Management 5.5.2-M5 Build 9fbbb857d0 (2019-June-27 13:27)

questions can be modified after upgrade

Generated at Mon Mar 01 05:01:11 UTC 2021 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.