ICEpdf
  1. ICEpdf
  2. PDF-1024

Custom SecurityCallback not applied in Viewer RI

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 6.1.2
    • Fix Version/s: 6.1.3
    • Component/s: Examples
    • Labels:
      None
    • Environment:
      Viewer RI

      Description

      I user reported that when implementing a custom SecurityHandler the handler was not being correctly attached and called when opening a document .

        Activity

        Hide
        Patrick Corless added a comment -

        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.

        Show
        Patrick Corless added a comment - 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.

          People

          • Assignee:
            Patrick Corless
            Reporter:
            Patrick Corless
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: