Indexed Security

When you enter a query, every object returned in the search results passes through the Live Collaboration kernel for access validation. Any objects you do not have access to, do not appear in the results.

This page discusses:

See Also
Configuring Indexing
Config.xml Parameters
Reference Information: MQL Indexing Commands

Workflow

By default, the config.xml file contains an access check for the CloudView server. It is based on the user access fields indexed for an object: 

<ACCESS check="true" useIndexedSecurity="true"/>

The following schema summarizes how indexed security works:



Limitations

On-Premises Environment

If the CloudView index cannot fully index the security linked to a 3DSpace object retrieved by a query, the object security is managed using post-processing. It may have the following impacts:

  • The number of results retrieved and displayed. The number of results displayed may be greater than the number of results retrieved.
  • Counts in the 6WTags may not be correct.
  • Some facets may display in the 6WTags but the user cannot see any objects in these facets.

Cloud Environment

For performance issues, security post-processing has been disabled. It means that all objects must have a security that can be fully indexed (non-secured objects cannot be retrieved).