"401 response with www-authenticate header causes browser native login prompt to be shown."
By sending:
WWW-Authenticate: AlfTicket realm="..."
We can avoid making the browser pop up a Basic auth dialogue box. This
is particularly useful for apps built for the browser that talk directly
to the Alfresco public APIs at the backend.
To use this feature, set alfresco.restApi.basicAuthScheme=false
Remove testCreatePersonWithInvalidCharacter() JUnit created in the prevoius commit, and modified testCreatePerson(), that previously verified creation of '/' to verify all 4 invalid characters.
Merged checking of '\' and '/' when creating groups into one single block that verifies all 4 invalid character in testCreateGroup() JUnit.
Added an char array containing illegall characters (/,\,\n,\r) to Groups and People API's, and adapted the checking of the previous illlegal character (/), to verify all of them.
Added two tests (one for group and one for people), creating using invalid id's.
When listing favourites through the REST API, the folders and files were showing the “title” in the description field rather than the “description”.
Fixed and also added a test.
- fixed by converting the initiator actual value to a ActivitiScriptNode instead of NodeRef. Still, the value passed in the response must be of type NodeRef
- added a check in WorkflowRestImpl for cases where customers already updated "initiator" process variable with type NodeRef
- added a Junit that checks also the "initiator" value after it is set using PUT request
* feature/REPO-437_Audit_REST_API: (26 commits)
REPO-1786 - Retrieve Audit Entries for a Node - minor code formatting
REPO-1786 / REPO-2668 / REPO-2669 - Retrieve Audit Entries for a Node - fix permission issue & update related JUnit tests
REPO-1786 / REPO-2668 / REPO-2669 - Retrieve Audit Entries for a Node - minor re-formatting & cleanup
REPO-1786 / REPO-2668 / REPO-2669 - Retrieve Audit Entries for a Node: - fixed a small issue: in case createdByUser is used in 'where' clause to retrieve audit entries for a node that were created by a user, a response code 400 was received. Now the audit entries are retrieved and response code 200 is received - fixed the case where createdByUser = 'me' is used in 'where' clause to retrieve entries for the current user - added a Junit test to cover these scenarios
REPO-1787 - Retrieve Audit Entry - return "values" by default for single audit entry
REPO-2555 / REPO-1787 - Retrieve Application Audit Entries (minor fix - return auditAppId not auditAppName)
REPO-2669 - REST API: Retrieve Node (alfresco-access) Audit Entries - add detailed JUnit tests (+ve & -ve): - refactored the tests to minimize code duplication
REPO-1519 / REPO-2642: REST API: Delete Application Audit Entries - implement API code - fixed a small bug: the response code was incorrect (response code 204) in case the parameters from 'between' clause were consecutive and inversed (e.g where=(id BETWEEN(2,1)) ). For this case a Response code 400 is received - added a Junit to test the above fix
REPO-2669 REST API: Retrieve Node (alfresco-access) Audit Entries - add detailed JUnit tests (+ve & -ve)
REPO-1519 / REPO-2645: Delete Application Audit Entries - add detailed JUnit test (+ve & -ve) - added Junits for +ve and -ve test cases for DELETE /audit-applications/{auditApplicationId}/audit-entries endpoint
REPO-2664: REST API: Delete Audit Entry - add detailed JUnit test (+ve & -ve) Correct the comment for the positive test (200 to 204 returned code for the positive test)
REPO-2598 : REST API: Retrieve Application Audit Entries - add JUnit test (+ve & -ve)
Revert "REPO-2598 Retrieve Application Audit Entries - add JUnit test (+ve & -ve)"
REPO-2598 Retrieve Application Audit Entries - add JUnit test (+ve & -ve)
REPO-2668 REST API: Retrieve Node (alfresco-access) Audit Entries - implement code
REPO-2661 - REST API: Retrieve Audit Entry - add detailed JUnit test (+ve & -ve) REPO-2664: REST API: Delete Audit Entry - add detailed JUnit test (+ve & -ve) Fix comments mistype( for Positive tests we recieve 200 status code instead of 400), convert audit-entry id from long to string at the start of the test instead of converting it on each API call.
REPO-2664: REST API: Delete Audit Entry - add detailed JUnit test (+ve & -ve) add test for delete audit entry +ve & -ve REPO-2661: REST API: Retrieve Audit Entry - add detailed Junit test (+ve & -ve) add 400 (Bad Request) scenario to the test.
REPO-2661 - REST API: Retrieve Audit Entry - add detailed JUnit test (+ve & -ve) Add Junit test +ve &-ve
REPO-2555 / REPO-1519 - Retrieve / Delete Application Audit Entries - fix ISO8601 parsing (eg. +0000)
REPO-2555 / REPO-1787 - Retrieve Application Audit Entries / Entry (fix user lookup)
...
* REPO-2792: add the new test suite structure based on application context
* REPO-2792: balance the tests in the job better
* REPO-2792: delete the old test suites
* REPO-2792: try another rebalance as the first job still had too much work
* REPO-2792: more balancing
* REPO-2792: balance after looking at the times of the tests in the surefire reports
