#2957 Console: Adding ACL from pki-console gives StringIndexOutOfBoundsException
Closed: fixed 6 years ago Opened 6 years ago by ftweedal.

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1546708

Description of problem:

Adding ACL from console gives:
ACLAdminServlet: java.lang.StringIndexOutOfBoundsException: String index out of range: -3

Version-Release number of selected component (if applicable):
10.5

How reproducible:

always
Steps to Reproduce:

  1. open pkiconsole
  2. Goto ACL on left panel.Add a testACL.
  3. Add resourcename=testACL, allowable rights=read,approve
    ACL entried add -- allow(read,approve)
    write description.
  4. Click on "OK".
  5. System logs shows
    ACLAdminServlet: java.lang.StringIndexOutOfBoundsException: String index out of range: -3

Actual results:

Expected results:

Additional info:

Audit logs doesn't report anything.

0.http-bio-25443-exec-25 - [19/Feb/2018:06:37:51 EST] [14] [6] [AuditEvent=AUTH][SubjectID=caadmin][Outcome=Success][AuthMgr=passwdUserDBAuthMgr] authentication success
0.http-bio-25443-exec-25 - [19/Feb/2018:06:37:51 EST] [14] [6] [AuditEvent=AUTHZ][SubjectID=caadmin][Outcome=Success][aclResource=certServer.acl.configuration][Op=modify] authorization success
0.http-bio-25443-exec-25 - [19/Feb/2018:06:37:51 EST] [14] [6] [AuditEvent=ROLE_ASSUME][SubjectID=caadmin][Outcome=Success][Role=Certificate Manager Agents, Administrators, Security Domain Administrators, Enterprise CA Administrators, Enterprise KRA Administrators, Enterprise OCSP Administrators, Enterprise TKS Administrators, Enterprise RA Administrators, Enterprise TPS Administrators] assume privileged role

Metadata Update from @ftweedal:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1546708
- Custom field type adjusted to None
- Custom field version adjusted to None

6 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

6 years ago

Merged to master:

  • 223e6980c3f3f7a075890897bbb74140cb95279a console: prohibit empty ACL expression
  • f62f8931d3dfced0b41e56e0bd4dc67fb31e2810 DirAclAuthz.updateACLs: re-throw ACL exception
  • 476320b43da7781a3f2994d55c8b48ee9bf6de73 ACLEntry.java: return null on parse error
  • 8f0b4a2f140590d6ed0149d9990e4f95eb047ae8 ACL.java: remove setDescription method
  • db05fc2c34b2f87e920d370cb5288ee0222f4023 ACL.java: retain all resourceACLs strings when merging
  • f4edd44009bc681577ea9209e092b65ca9985179 ACL.java: Make constructor private and add sanity check
  • f5e399a6bc7672d308332902d044e29f7deb3557 ACL.java: Remove unused constructor
  • 29092bd3a6c788164d3d37cdf40ac0811544accf Move parseACL to ACL.java

Metadata Update from @ftweedal:
- Issue set to the milestone: None (was: 0.0 NEEDS_TRIAGE)

6 years ago

Metadata Update from @ftweedal:
- Issue close_status updated to: fixed

6 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6.0

6 years ago

Pushed to DOGTAG_10_5_BRANCH:

  • c4904a4e39b2dd7ee6064ce04488aca36e19342d console: prohibit empty ACL expression
  • 021ebec5d54a85d8de56478fb4762c4b15ee0a3a DirAclAuthz.updateACLs: re-throw ACL exception
  • 682fcf270f6b49ff5a6e7133f022982445a74422 ACLEntry.java: return null on parse error
  • 5e36d86d2c5ab2264768e64fe8029e428ce01b92 ACL.java: remove setDescription method
  • 414a6a63d4833cfe0e575a682378fb9515ad59a6 ACL.java: retain all resourceACLs strings when merging
  • fcacf3d579a2562b764e0caed2cab81d73aa053f ACL.java: Make constructor private and add sanity check
  • 8748541f70e1c753589b37f76331a7cadc684253 ACL.java: Remove unused constructor
  • 80577d3480c8f5aa917db86f962b8acf6f750c55 Move parseACL to ACL.java

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.7 (was: 10.6.0)

6 years ago

Metadata Update from @mharmsen:
- Issue priority set to: critical

6 years ago

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

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.

Login to comment on this ticket.

Metadata