Hi, Anyone know what this means please: Plugin process wants to use confidential information stored in "v4.services.acrobat.com" in keychain?

That’s the Classic version. Maybe no update for it yet.

What exact version do you have today?

We just can't delete it from keychain?

For now I go to keychain app and select this "v4.services.acrobat.com" (click enter) and go to allow control or something like that (I have it in other language) and check first line "allow to all application". Maybe it helps.

Allen, are you sure that's the same issue?

Digging into this as well, started immediately after 10.13 OS upgrade upon launch of Acrobat DC. As we have several Apple OS systems at work subject to upgrade and have now tried several suggestions at this forum, and the problem persists, finally put a call into Adobe. The Adobe Rep did state this is a documented problem no fix until the next update cycle in November. At this will hang onto our case number and see what the next update cycle from Acrobat patches.

I've just started getting this popup recently - if I enter my password and choose Alway Allow, it still pops up again the next time I open safari. Same results for Deny. Yuck.

Is it possible this is related to "Captured Audience Platform" that Adobe chooses to implement for software use?.  When purchasing desktop version...one might still be partially captured via old plan?  

Insult to injury begins as we spend all of OUR time and OUR money trying to solve problems that are related to Adobes infrastructure.  I am bothered by the lack of value Adobe places on my time.  It's easy to prey on those who have no IT background.  Somewhat like predatory lending.  The most vulnerable consumers are those who have no understand of the particular business line.  I CHOSE to participate.  Yet I didn't know the full cost of participating with Adobe...until now.  

I have opened my keychain, and deleted the two apps that access this password. Seems to have solved it for now.

Delete "v4.service.acrobat" in keychain. Then it will not show up.

Update:

Adobe originally promised me a phone call after the first chat session. Yeah I didn't think that would actually happen and it didn't. In fact they waited an extra week and tried to tell me it wasn't their issue, it was Keychain and Apple's problem. I told them not to close the tick that the issue was in fact an Acrobat issue. A little over week later they just up and closed the case. I chatted again and told them to reopen it. I have spoken to Apple and they have verified that Keychain is up to date, installed properly, and functioning as it is programmed to function. This is what I added to the support ticket upon it being reopened:

First of all this case was closed rather than await my reply. The case is not withdrawn, it is not resolved and it is NOT an issue with Keychain.

I have contacted Apple and they have verified that Keychain is up to date, not corrupted and functioning exactly as programed. (Apple Case ID: *********).

Acrobat DC is calling to v4.services.acrobat.com, an Adobe Acrobat file to which it does NOT need access to function. Proof of which is that if you deny access 17-18 times the file will open and the plugin for the browser works perfectly.

The only reason that I am able to surmise that the PluginProcess (also an Adobe program) wants to access this is to take note of the files that are being opened. The identical file if saved to the local hard drive will not garner such an error. This is ONLY when accessed via the PluginProcess that is used exclusively with the browsers.

The PluginProcess Error occurs in all browsers, Safari, Firefox and Chrome. This is NOT an issue with Keychain, it is reproducible on multiple devices, and multiple people that are totally unrelated (see the thread Adobe Support quoted on June 1, 2015 below).

Closing this case rather than troubleshooting it is not a solution. Please address the issue and provide a solution that does not require access to my confidential information. It is confidential for a reason.

I look forward to your resolution.

Lets see what they say to this.

PS - part of their original solution was to refer me to this forum thread... AFTER I made my original comments. Doh!