Different returned document metadata depending on the query user

Jordi Masip

We realized we are obtaining different document metadata through CWS depending on the user who executes the same code.

If we want to retrieve next attributes:

List<String> attrSearch = new ArrayList<String>();

attrSearch.add("OTDataID");

attrSearch.add("OTName");

attrSearch.add("OTParentID");

attrSearch.add("OTSubType");

attrSearch.add("OTObjectSize");

attrSearch.add("OTCreateDate");

attrSearch.add("OTModifyDate");

We obtain next (from log file) using Admin user:

2014-09-03 09:55:30,670 [CategoryUtils.java:554] getNodeInfo:node.getS()---> 0: 119825

2014-09-03 09:55:30,670 [CategoryUtils.java:554] getNodeInfo:node.getS()---> 1: 2005 01 18 Inf.pÃºblica programa actuaciÃ³ integrada de la unitat d'execuciÃ³ Ãºnica Sector D del PGOU.pdf

2014-09-03 09:55:30,670 [CategoryUtils.java:554] getNodeInfo:node.getS()---> 2: 119604

2014-09-03 09:55:30,671 [CategoryUtils.java:556] getNodeInfo:SNode.Date.size=2

2014-09-03 09:55:30,671 [CategoryUtils.java:558] getNodeInfo:node.getD()---> 0: 2014-06-08T00:00:00+02:00

2014-09-03 09:55:30,672 [CategoryUtils.java:558] getNodeInfo:node.getD()---> 1: 2014-06-08T00:00:00+02:00

2014-09-03 09:55:30,672 [CategoryUtils.java:560] getNodeInfo:SNode.Integer.size=2

2014-09-03 09:55:30,673 [CategoryUtils.java:562] getNodeInfo:node.getI()---> 0: 230291

2014-09-03 09:55:30,673 [CategoryUtils.java:562] getNodeInfo:node.getI()---> 1: 144

2014-09-03 09:55:30,674 [CategoryUtils.java:564] getNodeInfo:SNode.Double.size=0

While we obtain less information with a less privileged user:

2014-09-03 10:21:59,804 CategoryUtils.java:552] getNodeInfo:SNode.String.size=1

2014-09-03 10:21:59,805 [CategoryUtils.java:554] getNodeInfo:node.getS()---> 0: 2005 01 18 Inf.pÃºblica programa actuaciÃ³ integrada de la unitat d'execuciÃ³ Ãºnica Sector D del PGOU.pdf

2014-09-03 10:21:59,805 [CategoryUtils.java:556] getNodeInfo:SNode.Date.size=0

2014-09-03 10:21:59,805 [CategoryUtils.java:560] getNodeInfo:SNode.Integer.size=1

2014-09-03 10:21:59,806 [CategoryUtils.java:562] getNodeInfo:node.getI()---> 0: 230291

As you can realize, node ID or dates are not retrieved in the second case, for instance.

Any explanation?

Find more posts tagged with

Comments

Kevin_Mark

My first thought is that this was done for security reasons.

As for modified date, it is possible that knowing when a document was modified is reason enough to restrict that info from unauthorized users.

Kevin_Mark

Could you provide me the exact CWS calls you used?

Jordi Masip

I think it isn't a permission problem.

If I'm able to retrieve creation or modification date accessing to the same Content Server information through browser using less privileged user, I would expect the same behaviour accessing to the same information with the same user through CWS, wouldn't I?

Below you can read related code:

String whereClause = "\"OTCurrentVersion\":\"TRUE\" AND QLRIGHT-TRUNCATION \"Ripoll\" AND \"Attr_39389_7\":\"04 - Transformación de suelo\"";

SingleSearchRequest query = new SingleSearchRequest();

query.setDataCollectionSpec("'LES Enterprise'"); // use the first search slice in the list

query.setQueryLanguage("Livelink Search API V1"); // use the Search API for queries

query.setFirstResultToRetrieve(1); // start retrieving results at Result #1

query.setNumResultsToRetrieve(500); // retrieve up to 1 search results

query.setResultOrderSpec("sortByRegion=OTCreatedBy"); // sort by the OTCreatedBy region

query.setResultSetSpec("where1=" + whereClause); // set the where clause of the query

// set the displayed/retrieved regions for each result

query.getResultTransformationSpec().addAll(attrSearch);

SingleSearchResponse search = searchService.search(query, "");

if (null != search) {

return search.getResults();

} else {

return null;

}

Kyle_Swidrovich

Are those regions marked as Displayable on the Enterprise Search Manager's Regions page?

There is no such thing as metadata region "permissions" in search.

Search also isn't aware how the metadata was derived. That is, it doesn't know where "OTModifyDate" data originally came from and it has no permission information about that.

For that reason, administrators need to consciously decide which regions they want to allow users with See+See Contents on the item being returned to see information on. This decision is made through marking the region as "Displayable" on that regions page.

Jordi Masip

Marking attributes as displayable in region map solved the problem.

Two points were misleading:

- Admin user was able to retrieve the information through Webservices using the same code while other less privileged CS user didn't.

- Expected information through webservices using limited user was available through standard GUI access with the same limited user.