[OPENAM-6056] LoginViewBean does not correctly handle empty ChoiceCallbacks Created: 26/May/15 Updated: 20/Nov/16 Resolved: 19/Jun/15
|Affects Version/s:||12.0.0, 13.0.0|
|Fix Version/s:||11.0.4, 12.0.3, 13.0.0|
|Reporter:||Quentin CASTEL [X] (Inactive)||Assignee:||Quentin CASTEL [X] (Inactive)|
|Time Spent:||Not Specified|
|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
|Comment by Quentin CASTEL [X] (Inactive) [ 19/Jun/15 ]|
Fixed in 13.0.0 in r14287
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.
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.