Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

SSL error while opening secured documents

livecycle_dive
Level 2
Level 2

Rights_Management_error.JPGRights_Management_error.JPG]

I am getting this error after rights management policies have been downloaded and applied on the document. I confirmed that security certificate is in my certiifcate store (trusted). Does it need to placed at any other place too ? What could I be possibly missing here ?

1 Accepted Solution
SForrest96
Correct answer by
Level 9
Level 9

Did you set the Base URL property for Rights Management to use the proper (SSL) URL?

See screen shot.

Steve

View solution in original post

4 Replies
SForrest96
Correct answer by
Level 9
Level 9

Did you set the Base URL property for Rights Management to use the proper (SSL) URL?

See screen shot.

Steve

View solution in original post

livecycle_dive
Level 2
Level 2

Yup,...That worked....!!!!

Appreciate your quick help.    

livecycle_dive
Level 2
Level 2

Couple of more areas that I want to seek further inputs. While version 9 - STD allows me to refresh policies and save the new secured doc, the same is not applicable to ACROBAT PRO X. Also, I believe I am adding creating users but when I try to find them while creating policies, I simply can't locate the users. Anything that I am missing ?    

SForrest96
Level 9
Level 9

Im not sure what you mean by the same is notapplicable to Acrobat Pro X, you can certainly use Acrobat Pro 10 to apply policies to PDF documents.  Is it that you can't locate where to refresh the policies?  Have you configured the Advanced settings in Acrobat 10 so it knows which RM server to pull the policies from?

You need to set it up under Tools > Protection > More Protection > Security Settings.  See screen shots.

As for the uses being available whencreating policies, you need to make sure that you have properly configured the "Visible Users and Groups" for the policy set that you are creating the policy in.  Only users in the domains that are added to "Visible Users and Groups" will be available to be added to the policy.

Regards

Steve