The current JSS API is based on an old NSS API which can only access a single database for the whole duration of the JVM. It doesn't seem to be possible to access multiple databases, either concurrently or consecutively, without restarting the JVM.
NSS provided an explanation why this is a problem and provided a new API as a solution: https://wiki.mozilla.org/NSS_Library_Init. The JSS API would have to be updated to use the new NSS API.
The NSS problem described above doesn't necessarily apply to Dogtag, but there might be situations where it can be useful to support multiple databases:
Per CS/DS meeting of 04/28/2014 - 10.4.
Additionally, it was discussed in this meeting to also move PKI TRAC Ticket #167 - Update Dogtag 10 to utilize the shared NSS database model to 10.4.
Metadata Update from @edewata: - Issue set to the milestone: UNTRIAGED
<rcrit> cfu, jmagne, mharmsen not sure if you saw this but Kaie is proposing to switch the NSS to default to sqlite format in F-27. https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql <mharmsen> rcrit: thanks -- we were not aware of this, but we do have a long-standing ticket for it -- https://pagure.io/dogtagpki/issue/167 <rcrit> yeah, I figure it'll up the timetable on these <rcrit> 389-ds has a similar ticket, https://pagure.io/389-ds-base/issue/48760 <mharmsen> rcrit: also https://pagure.io/389-ds-base/issue/47681 <rcrit> Ok, I'll let Mark know so he can close one as a dup <mharmsen> rcrit: yep <mharmsen> rcrit: just scanned Kaie's doc, but will they have a flag to create the old NSS db format? <rcrit> you have to specify dbm:/path/to/nss/database
Metadata Update from @mharmsen: - Custom field cc adjusted to mreynolds@redhat.com,rcrit@redhat.com - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: None - Issue priority set to: blocker (was: major) - Issue set to the milestone: 0.0 NEEDS_TRIAGE (was: UNTRIAGED)
This is the push we need to finally start using the new DB format.
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 0.0 NEEDS_TRIAGE)
See also https://pagure.io/dogtagpki/issue/1176
Upstream JSS ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=1397824
Metadata Update from @mharmsen: - Issue priority set to: critical (was: blocker)
Metadata Update from @mharmsen: - Issue priority set to: major (was: critical)
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1540
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.