Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Document Library Repository Remote Staging causes Principal Exception

Description

To test:

  1. Startup CMIS repository

  2. Startup and login to two portals

  3. On Portal 1, mount the CMIS repository.

  4. Configure staging of Portal 1 and publish to Portal 2

  5. Error will occur, with Portal 2 having a Principal Exception in stack trace:

Activity

Show:

Tammy Fong November 8, 2012 at 1:49 PM
Edited

PASSED Manual Testing following the steps in the description.

Fixed on:
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: d0297e3a439fff89052b98229e402b3c208fde61.

No exceptions will occur when Portal 1 remotely publishes to Portal 2.

Tammy Fong September 10, 2012 at 10:48 PM

FAILED Manual Testing following the steps in the description.

Reproduced on:
Tomcat 7.0 + MySQL 5. Portal 6.1.10 EE.

Principal Exception will occur in Portal 2 when Portal 1 remotely publishes.

Fixed on:
Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: 79afed965e35b5a8e44d89e38952cdf5334c1ffb.

No exceptions will occur when Portal 1 remotely publishes to Portal 2.

Failed on:
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: e36575c21a8fa1e6dbf519234021973e28defdfb.

Portal 1 remotely publishes to Portal 2 without exceptions, however when the CMIS repository is opened in Portal 2, the following exceptions occur:

Fixed

Details

Assignee

Reporter

Labels

Branch Version/s

6.1.x

Backported to Branch

Committed

Fix Priority

4

Git Pull Request

Components

Fix versions

Affects versions

Priority

Zendesk Support

Created June 13, 2012 at 12:49 PM
Updated June 24, 2023 at 3:50 PM
Resolved November 8, 2012 at 2:19 PM
Loading...