Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

single sign-on through documentum:

Avatar

Former Community Member

Hello everyone..

  here is my scenario: We have documentum repository and the users see the respective files using their user id & password through documentum taskspace. We want to sync the LDAP with Livecycle and apply RM policies to all the documents to the repository using the LC process. So, if user logs in & click on a document to open it, it should automatically check his credentials and the document should be open if the user is defined in the policy. This avoids entering their user id & password again for each document.

  How do we make this single sign-on happen? I'm sure that RM provides it. But I'm not getting the steps or proper document on how to implement it. Also I'm beginner in implementing RM.

One more question: I checked applying the policies to document and opening it through other PC. I observed that we need to install the SSO certificate so that it will connect to LC server to validate his credentials. Do we need to ask every user to install the certificate for them to open the policy applied documents? Even if all the users are in the internal network of organisation?

Please help.

Thanks,

Krishna

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Krishna

I'm not sure if I understand your last entry completely, but let me clarify... Rights Management does not use digital certificates (asymmetric encryption) to encrypt documents.  Encryption is done using symmetric or "secret" key encryption with Advanced Encryption Standard (AES) keys at 128 or 256 bit key strength.  No certificates need to be installed on any indvidual systems.

The AES keys are stored and managed on the RM server, when opening a protected document on "online" mode, the key is delivered to the client machine so the document can be decrypted, the key does not reside on the client machine.

Regards

Steve

View solution in original post

10 Replies

Avatar

Former Community Member

Any help on this please?

  Also, just got one more question from my client. If the document is taken offline (if policy is given offline permissions for 10 days lets say & it got print premissions), the user can take the document on his thumbdrive. What if the user prints it? I'm sure that this event will not be logged in Livecycle.

   Is it possible to disable printing when the document is taken offline. And we want to enable print option is the document is online. Atleast this way, we can keep track of who printed the document.

Thanks in advance,

krishna

Avatar

Former Community Member

If the policy has "auditing" turned on, events that occur when the document is offline will still be logged and stored locally, and then uploaded to the RM server when a connection is re-established.

It is not possible to enable\disable permissions based on whether the document is opened online or offline.

Regards

Steve

Avatar

Former Community Member

Hi Steve,

  Thanks for your reply. I understand about logging all the events once we synchronize the document from offline to online.

But we are concerned about the documents that were not brought back online. As we cannot get the info on whether he printed the document or not,

atleast we want to make the document non-printable so that user should not print it.

Is that possible. Also, all users are eligible for viewing the documents, so there is no point for making each user to enter his credentials to view the document. If user clicks on the print button, we want the document to check in rights management to check the user credentials and apply a policy to disable him to print the document or just message him saying that he is not eligible to print it. This way, we can avoid unnecessary entry of credentials for all users and also we can reduce the traffic of contacting rightsmanagement server. We can contact RM server only for a few users as only few users will try to go for printing the document.

Can we make this possible?

krishna

Avatar

Former Community Member

Permissions specified in a policy for each user and or group are enforced whether the document is viewed online or offline.

You can create an "Anonymous User" policy and apply it to the document.  When using "Anonymous" policies, users are NOT authenticated when the document is opened, one of the trade offs however is that the permissions specified in the policy are "global" ,eaning you cannot set diffierent permission for different users.  Either all users can print, or no users can print.

If you create a policy where specific users and groups are identified, then each user must authenticate to open\view the document, but you can set the permissions for each user and\or group indvidually. Some can be allowed to print, and some can be prevented from printing.

Whan a user has been granted the "offline" permission, the policy permissions are still enforced.  When viewing the document offline, the user will not be prompted to authenticate to view the document, although authentication still takes place, as they will have authenticated (logged on) to their computer.  The "principal" key used to decrypt a document offline is stored under the users system (i.e. Windows) profile.  For example, if Joe User has been granted offline permission, and Joe User logs onto his computer he will be able to view the protected document.  If another user, Chester Field logs onto Joe User's computer, he will NOT be able to view the document offline as he doies not have access to Joe User's profile information.

You cannot authenticate based on a users action (i.e. clicking the print button), the user must authenticate prior to viewing the document (except in the case of an Anonymous policy).

Hope this helps.

Steve

Avatar

Former Community Member

Hello Steve,

  Thank you for the response. Your answer helped us a lot.This raised one more question to us.

1.  If we create a policy on document to take it offline, till date we are presuming that the document can be taken on thumb drive or cd and can be   opened on any system without connecting to server. This is not true for policy applied documents. Am I right? Can we make this possible? You may ask why. We want the document to be invalidated after 3 days once it is taken offline and we dont mind who ever opens it on what ever system it is, but we want it to be gone after 3 days.

2. We have 5000 users who connect to our documentum with their credentials where we have our policy applied documents. Do we need to install the certificate on all the systems? Or do we generally install the certificate on documentum server so that who ever user logs in to documentum, will be eligible automatically to view the document? I mean the single sign access to documents. Can you give some inputs on developing a poc on this?

Thanks again,

Krishna

Avatar

Former Community Member

Krishna

When a user has the permission to view a document offline, they can only view the document on computers where the corresponding "Principal" key has been downloaded.  The "Principal" key(s) are downloaded in a few ways

1)  The first time a user opens a document where they have offline permissions, they are prompted to downloed the principal key

2)  When the user authenticates to open policy protected documents, a check is performed and principal keyts may be updated

3)  The user can force a "synchronization" form Reader or Acrobat from the menu:  Document > Security > Adobe LiveCycle Rights Management > Synchronize for Offline

For a document to be opened offline, a Principal key MUST reside on the computer used to view the document.  There is now way around this.

As for SSO with Documentum, this is not possible.  Rights Management supports SSO to the document via Microsoft Kerberos with Active Directory.  That being siad, there are some features that exist to limit the amout of time a user has to authenticate.  When a user authenticates to a protected document, a session is established (the session timeout can be configured on the server), if the user does not close Acreobat or Reader, they will not be prompted for their credentials when opening subsequent policy protected documents where they are a member of the policy.

You can also enable "credential caching" on the server so that a users credentials will be cached on the client.  Once stored on the client the user will not be required to enter their user id and password to open policy protected documents where they are a member of the policy.

Regards

Steve

Avatar

Former Community Member

Thanks a lot Steve.

I understood what you were saying about entering credentials part.

I was not clear on one last question - Does it mean the RM certificate needs to be installed on all the individual systems for viewing policy enabled documents right? No matter if it is 5000 or 10,000 users?

Our documentum works in sync with LDAP.

--Krishna

Avatar

Correct answer by
Former Community Member

Krishna

I'm not sure if I understand your last entry completely, but let me clarify... Rights Management does not use digital certificates (asymmetric encryption) to encrypt documents.  Encryption is done using symmetric or "secret" key encryption with Advanced Encryption Standard (AES) keys at 128 or 256 bit key strength.  No certificates need to be installed on any indvidual systems.

The AES keys are stored and managed on the RM server, when opening a protected document on "online" mode, the key is delivered to the client machine so the document can be decrypted, the key does not reside on the client machine.

Regards

Steve

Avatar

Former Community Member

Thanks for your prompt answers Steve. It helped a lot.

Krishna

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] ----