Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Files protected by LiveCycle Rights Management 9 are not indexed?

Avatar

Level 2

Hi everybody, I have a question, files protected by LiveCycle Rights Management 9 are not indexed?  is that true?

Regards.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

When you create a policy, one of the properties that you set determines what gets encrypted when the policy is applied to a document.  You can set it to...

  1. Encrypt the entire file, which means that the document could not be searched\indexed as all of the document contents, including any meta data are in an encrypted state.
  2. Encrypt the document except meta date, which means that the document can be searched\indexed based on the meta data as it is NOT encrypted
  3. No Encryption, which means that the document, including any meta data is not in an encrypted state, and can therefore be searched\indexed.

Hope this helps.

Steve

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

When you create a policy, one of the properties that you set determines what gets encrypted when the policy is applied to a document.  You can set it to...

  1. Encrypt the entire file, which means that the document could not be searched\indexed as all of the document contents, including any meta data are in an encrypted state.
  2. Encrypt the document except meta date, which means that the document can be searched\indexed based on the meta data as it is NOT encrypted
  3. No Encryption, which means that the document, including any meta data is not in an encrypted state, and can therefore be searched\indexed.

Hope this helps.

Steve

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----