This issue occurs when a user is using Alfresco with Kerberos. The user clicks on the WebDav link in Explorer on the document details page and receives a 500 error message in the browser. The log file shows:
"a valid SecureContext was not provided in the RequestContex"
There is another JIRA with the same information (see https://issues.alfresco.com/jira/browse/MNT-12097). A customer sees this with Alfresco Enterprise 4.2.2 and I was able to replicate it. Scott Ashcraft asked me to test this with a QA version of 4.2.4 which is likely the target version of the fix in
MNT-12097 but I was still able to replicate this. Perhaps this fix has not been implemented on 4.2.4 yet but I'm not sure.
Steps to Replicate:
1. Install Alfresco 4.2.2 (and 4.2.4 build pulled on August 21, 2014 by me from pbld01) and setup with Kerberos authentication using Active Directory user repository.
2. Go to Alfresco Explorer and upload testfile1 to a space.
3. Go to the Document Details for testfile1.
4. Click on the WebDav url.
The WebDav url should render the file like the CIFS url does or at least without error.
A 500 Error is shown on the page and in the logs is a "valid SecureContext was not provided in the RequestContex" error.
Customer Urgency/Expectations: The case is a Sev 4/Enterprise. Urgency does not appear high but since they are an Enterprise customer they may request a HotFix though this doesn't appear to be a critical need.
Expected Fix Release: 4.2.x Service Pack or if HF request, 4.2.2.x