[OPENAM-6056] LoginViewBean does not correctly handle empty ChoiceCallbacks Created: 26/May/15  Updated: 20/Nov/16  Resolved: 19/Jun/15

Status: Resolved
Project: OpenAM
Component/s: authentication
Affects Version/s: 12.0.0, 13.0.0
Fix Version/s: 11.0.4, 12.0.3, 13.0.0

Type: Bug Priority: Major
Reporter: Quentin CASTEL [X] (Inactive) Assignee: Quentin CASTEL [X] (Inactive)
Resolution: Fixed Votes: 1
Labels: EDISON, release-notes
Remaining Estimate: 1h
Time Spent: Not Specified
Original Estimate: 1h

Issue Links:
duplicates OPENAM-4968 LoginViewBean does not correctly hand... Resolved
Target Version/s:
Sprint: Sprint 82 - Sustaining, Sprint 83 - Sustaining
Support Ticket IDs:


If you send a ChoiceCallbacks with no selection in it, LoginViewBean forces it to "0".

Custom Authentication module are not to do the difference between an empty ChoiceCallBacks or the choice "0".

Comment by Peter Major [X] (Inactive) [ 16/Jun/15 ]

I can only assume this is a duplicate of OPENAM-4968

Comment by Quentin CASTEL [X] (Inactive) [ 19/Jun/15 ]

Fixed in 13.0.0 in r14287
Fixed in 12.0.2 in r14288
Fixed in 11.0.4 in r14289

Important note about this fix:

Now, it's possible to know if there user send an empty callback. It won't be forced to "0" anymore but the selected value will be null.

Since this fix, it's now possible that ".getSelectedIndexes()" returns null.
Custom authentication module should be aware of this change and should implement this new case.

In which case, the null value for the SelectedIndexed is useful?

If you decided to implement a single checkbox with a ChoiceCallback, you will need to distinguish the unselected checkbox value to the selected value. For implementing this kind of case, you will need this fix.

Generated at Thu Jan 21 11:24:54 UTC 2021 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.