Details
Description
I user reported that when implementing a custom SecurityHandler the handler was not being correctly attached and called when opening a document .
Activity
Patrick Corless
created issue -
Patrick Corless
made changes -
Field | Original Value | New Value |
---|---|---|
Fix Version/s | 6.1.3 [ 13086 ] |
Patrick Corless
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #49205 | Tue Sep 13 10:20:05 MDT 2016 | patrick.corless | |
Files Changed | ||||
MODIFY
/icepdf/branches/icepdf-6.1.0/icepdf/viewer/src/org/icepdf/ri/common/SwingController.java
|
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #49493 | Tue Nov 08 10:49:19 MST 2016 | patrick.corless | |
Files Changed | ||||
MODIFY
/icepdf/trunk/icepdf/viewer/src/org/icepdf/ri/common/SwingController.java
|
Patrick Corless
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
When using the Document class the security callback works as expected. The Viewer RI is a bit different as it requires the securityCallback be set on the documentViewController. There is a bug in the API that prevents the new security callback from being set on the document when a document is opened for the first time. There are ways around this by directly applying it to the document class however it is clumsy.
This fix insures that a call to controller.getDocumentViewController().setSecurityCallback(e ->{}) works as expected.