dogtagpki

#2620 User with userid length 10000 char is not get deleted .
Closed: migrated by dmoluguw. Opened by mharmsen.

Closed: migrated
Reopen Issue

I added the user with userid as random string which has length 10000 char, User
is get added in to the database. But while try to delete the user it won't
delete it, and it throws an exception.

Steps to Reproduce:

  1. t=openssl rand -base64 80000 | strings | grep -io [[:alnum:]] | head -n 10000 | tr -d '\n'
  2. pki -d nssdb_test/ -c Secret123 client-init
  3. pki -d nssdb_test/ -c Secret123 -h pki1.example.com -p 20080 client-cert-import --pkcs12 /opt/topology-02-CA/ca_admin_cert.p12 --pkcs12-password Secret123
  4. pki -d nssdb_test/ -c Secret123 -h pki1.example.com -p 20080 client-cert-import CA --ca-server
  5. pki -d nssdb_test/ -c Secret123 -h pki1.example.com -p 20080 -n "PKI CA Administrator for Example.Org" user-add --fullName="Test USer" $t
  6. pki -d nssdb_test/ -c Secret123 -h pki1.example.com -p 20080 -n "PKI CA Administrator for Example.Org" user-del $t

Actual results:

IllegalStateException: Invalid use of BasicClientConnManager: connection still allocated.

Make sure to release the connection before allocating another one.

Expected results:

User should be deleted.

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1430237

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1430237

Metadata Update from @mharmsen:
- Custom field component adjusted to General
- Custom field feature adjusted to ''
- Custom field origin adjusted to QE
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field type adjusted to defect
- Custom field version adjusted to ''

This scenario seems rather unlikely to be encountered by users.

Proposing: FUTURE - minor

Metadata Update from @mharmsen:
- Custom field proposedmilestone adjusted to FUTURE (was: '')
- Custom field proposedpriority adjusted to minor (was: '')

Per PKI Bug Council of 03/30/2017: FUTURE - minor

Metadata Update from @mharmsen:
- Custom field proposedmilestone adjusted to '' (was: FUTURE)
- Custom field proposedpriority adjusted to '' (was: minor)
- Issue priority set to: minor
- Issue set to the milestone: FUTURE (was: 0.0 NEEDS_TRIAGE)

Per 10.5.x/10.6 Triage: FUTURE

RHBZ: CLOSED UPSTREAM

alee: error test case

Metadata Update from @mharmsen:
- Custom field rhbz reset (from https://bugzilla.redhat.com/show_bug.cgi?id=1430237)

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/2740

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

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)
Metadata
None
None
None
None
High
None
''
''
''
''
''
defect
General
QE
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.