Closed pki-bot closed 4 years ago
Comment from ftweedal (@frasertweedale) at 2017-01-23 08:50:44
I'm on this.
Comment from ftweedal (@frasertweedale) at 2017-01-23 09:47:24
attachment pki-frasertweedale-0149-Use-BigInteger-for-entryUSN.patch
Comment from edewata (@edewata) at 2017-01-23 21:06:05
Fixed in master:
Comment from mharmsen (@mharmsen) at 2017-01-26 19:55:31
Moving to 10.3 critical based upon associated bug
Comment from msauton (@msauton) at 2017-01-27 23:30:35
fix corrected the behavior when having high entryusn values in the o=ipaca ipa's dogtag backend, no more exception, and proper CA start, thanks.
Comment from mharmsen (@mharmsen) at 2017-01-28 02:56:36
Replying to [comment:4 edewata]:
Fixed in master:
- 79c6d70a8434cf52f9bac8bfa0367876baccb054
Cherry-picked to DOGTAG_10_3_BRANCH:
Comment from edewata (@edewata) at 2017-02-27 14:01:36
Metadata Update from @edewata:
This issue was migrated from Pagure Issue #2579. Originally filed by edewata (@edewata) on 2017-01-16 23:32:48:
Under certain circumstances the LDAPProfileSubsystem may generate NumberFormatException because it's trying to parse an entryUSN value greater than the maximum range of an Integer.
A possible solution is to use BigInteger instead of Integer.