Adobe Reader 9 - proxy authentication

Since updating to AR9 when checking for updates an "Adobe Reader Updater" window appears indicating that "proxy authentication is required" and asking for username and password, which on adding the (full) name and password for our proxy redisplays the window.
On cancelling you get the error 1400.
What / Whose proxy is this ? How do you set it ?
Thanks

The Adobe Updater is attempting to bypass the standard ISA client authentication by initiating a connection as an Anonymous User rather than allowing the client to connect as a domain member. Why this would be designed this way is another question.
Do not change the Proxy settings on your clients, it will have no effect on the Adobe Updater and may disable other functions - you know, the ones that were properly written.
You will need to create a new ISA rule allowing all users in the protected network access to either a created URL set or Domain set as shown below, whichever you prefer.
Domain set --
adobe.com
*.adobe.com
URL set --
http://armmf.adobe.com:443
http://crl.adobe.com/*
http://swumpf.adobe.com/*
https://armmf.adobe.com:443
https://crl.adobe.com/*
https://swumpf.adobe.com/*

Similar Messages

Mac Adobe Flash Player not supporting Web Proxy Authentication

Anyone else got an enterprise network where you use web proxies with web authentication and no traffic allowed out except through the proxies?
You may need to be in the UK for this, but try accessing BBC iPlayer content - http://www.bbc.co.uk/iplayer and you should discover that the content won't play. the error says "This content doesn't seem to be working. Try again later.". The content will never work as the Mac version of Flash (currently 10.1.53.64) is not able to respond to web proxy authentication requests. The BBC use various streaming server which are randomly selected when a user starts a stream and they have no DNS. Just IP addresses. They don't publish a list for security reasons. So it is almost impossible to exempt all their servers from authentication.
I've logged a bug with Adobe. If you have this issue too, please add a comment and vote so that they can begin to grasp the impact of this problem:
https://bugs.adobe.com/jira/browse/FP-5161

I have the same issues in Australia trying to access flash content from the ABC website. The strange thing is the content will play if your leave the browser open for 5min.
After several packet data captures we identified that it has to do with the amount of time it takes the Mac timeout from the proxy before it plays the video content.
No solution yet.

Adobe Reader 9.0 has delay when downloading PDF file through proxy server

There is an issue with the Adobe Reader (and Acrobat) 9.0 PDF Link Helper ActiveX control for Internet Explorer (6 or 7) on Windows computers with respect to proxy servers. Due to this issue, there is a 2 minute delay for any Internet Explorer web browser on the Deere network before any PDF file will open from the Internet within the IE web browser if In-Place activation (Display PDF in Browser) is enabled in Adobe Reader 9. This problem does not affect Adobe Reader 8.
What we are seeing is that when someone on the Deere network clicks on a links to a PDF file in the Internet, the PDF file downloads immediately. But then, after the PDF file is downloaded, the Adobe Reader 9 PDF Link Helper ActiveX control tries to talk directly to the Internet web site. The Adobe Reader 9 PDF Link Helper ActiveX control does not know how to negotiate our proxy server. So after a minute or two, the Adobe Reader 9 PDF Link Helper ActiveX control times out (gives up) and allows the IE browser to display the downloaded PDF file in the IE browser.
We work around this issue by disabling In Place Activation for PDF files in IE (uncheck Display PDF in Browser). But we would like a fix for the PDF Link Helper ActiveX control.
[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\9.0\Originals]
"bBrowserIntegration"=dword:00000000
[HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\9.0\Originals]
"bBrowserIntegration"=dword:00000000
Here's what our proxy people see when they do a trace of a PDF file download through their proxy server with IE 7 and Adobe Reader 9 with Display PDF in Browser checked.
The browser tells the proxy to download the pdf, it does and sends it to the browser. Before the browser opens it something in Acrobat ( or I.E. ? ) tries to make a connection back to the content server that hosted the pdf. Unfortunately this agent does not ask the proxy to make the request for it, but rather asks local DNS to resolve the Internet server name. This request dies because our internal private network does not know anything about the Internet. Only the DNS used by the proxy can resolve Interent names. After two unsuccessful DNS queries into the private network, the agent tries to resolve the same Internet name with NBNS ( netbios name service) queries again into the private network, with the same results. These requests persists for more than two minutes ( over 200 unresolved queries ). Then for whatever reason the agent gives up and the already downloaded pdf file loads into the browser.
I have a TCP capture file if you want it.

Hi,
I have the same problem with some specific PDF files. For more than 90% it hangs when opening the file, but sometimes it works (with the same file).
The workflows where it sometimes worked:
a) Loading the PDF, the reader is started the first time and displays license dialog.
b) The reader was already runing and file is loaded with Drag&Drop or File/Open in the Reader
But most times it does not load.
I could not find out which file is missing or trying to be opened. So I tried with the CP949.TXT.
I found no CP949.TXT in Reader 8 installation, so I took it from the link, pasted into notepad and stored in the respective directory
C:\Program Files (x86)\Adobe\Reader 9.0\Resource\TypeSupport\Unicode\Mappings\win\
Now it seems to work fine, opening PDFs with double click from exporer.
But why did Adobe Reader 8 not have the TypeSupport directory at all?
Even when having found a fix (hack?), I think I did not understand the cause of this problem.
Regards,
TheLastReader

Adobe Reader doesn't remember the output method user authentication

Here's the setup:
We use a network printer that is set up only using user inboxes with user authentication. There's no normal printing.
The printers are set up on the mac computers using output method > user authentication > userid and password.
This works fine for every application, but somehow it doesn't for Adobe Reader. It 'forgets' the password every now and then,
even if when you look at the user authentication, the setting is still checked, and the password is still filled in.
if I reinsert the password, and press OK, then press Print, the task is sent to the printer again, only this time, it actually prints.
I can't think of a reason why Adobe Reader won't remember the settings.

Merry Christmas!
I currently only have Adobe Reader 9 installed.
I did uninstalled Adobe and Acrobat, run a registry clean up....then installed Adobe Reader 9.
but still not working.
Very strange that everytime i open the program from Start-->Adobe-->Adobe Reader 9, then it starts install Reader.....it says please wait while Adobe install, it takes another 2 minutes then it opens.
If I open by double click on the.pdf file, it then ask what program do you want to open this file. I selected Adobe Reader 9, then it opens without any installation windows.

Why do I keeping getting proxy authentication request when trying to read Gmail?

I am behind a Blue Coat proxy, whenever I try to hit gmail or google play, I get a pop-up that request user authentication (moz-proxy). I have seen a number of post on this and tried the fixes. Nothing seems to help. When I tried this: https://support.mozilla.org/en-US/questions/943488, Step three: network.automatic-ntlm-auth.allow-proxies – FALSE, I was block from hitting any webpage. I have tried opening is SAFE MODE, that did not work. Are there any other solutions?

"IE’ uses windows authentication, and authenticates with proxy server silently behind the scenes. Chrome uses IE’s settings in windows, for proxy settings. Hence the same behavior as IE. But Firefox, tries to do it on its own, that is why it tries to authenticate and find out if you have access to the site.
But, yeah, for your problem, the best way would be to ignore proxy for the site if you know they are already blocked."
Reference: http://nasarabna.wordpress.com/2010/03/03/firefox-keeps-prompting-for-proxy-authentication/

Can't download Adobe Reader, proxy issue?

I'm trying to download reader 10.0.1 in English using 64 bit Windows 7. After I downloaded the download manager I am prompted with the message " In order to use a proxy, please enter the following data and ensure you are connected to the internet." And then I'm asked for an address and then a port.
I have no idea what this message means. Any help would be greatly appreciated. Thank you

Hello,
Download the Offline installer for Adobe Reader X from this link :
ftp://ftp.adobe.com/pub/adobe/reader/win/10.x/10.0.0/en_US/AdbeRdr1000_en_US.exe
Once its download you can run it and it will install Adobe Reader X.
Hope it helps !!
Thanks,
Vikram

Programatically reading browser proxy settings & authentication

hi,
doesn anyone know to read the default browser proxy settings while proxy requires authentication? I would have to set the proxy address together with username and password to a XFire client... and would have to extract them somehow somewhere.

Nevermind about this, I managed to figure out a workaround. This was actually question about XFire and Commons HTTPClient -- it seems that java web start is unable to pass on proxy information to Commons HTTPClient. Instead using java HTTPUrlConnection worked with proxy authentication, so I'm content with this solution, at least so far. Seems to be a "feature" in commons package.

As we want to develope a plug-in in adobe reader, what we need to do or follow, and about authentication. Thank you!

We need to develope our own adobe reader plug-in, what we need to do to follow the developing.
When we had finished developing our own adobe plugin, we need the adobe plug-in to be released so that our user can click a link to download and install our plugin. It should be given the appropriate authorization adobe. We need to understand the process of development and publishing plug-ins as well as expenses that may arise here.

Thanks for your reply. And there is another thing that is when we had finished the developement of the plug-in. We dont't know whether we need to connect to adobe to licensed to us so that our users can install the plug-in in reader. And of course, is there any costs we need to pay for about the licence.~~~

Any known problems using IE6 and Adobe Reader 7 with LC:RM?

On an properly configured LC:RM server only allowing certificate (X509) authentication,
Adobe Reader 7 always pops up some Username/Password dialog for authentication.
Reader 8 and 9 work fine with certificates.
Is this an known restriction, that
Reader-7 does not support X509 authentication?
Dilettanto

Steve,
thank you again for your helpful answer.
In addition we now found out, that Users having an authenticating Proxy
may even need to upgrade to Adobe Reader 9 to be able to use LC:RM.
Dilettanto

Acrobat Standard Proxy Authentication

Hi,
When we sign our PDF's we want to use an external timestamping server
So we have configured both a Verisign and Globalsign timestamping server and made one of them as default
Most of the time we got a response from Acrobat saying
"Timestamp signature property generation error:
Transport authorization failure"
When it fails the doc is signed, but using the computers clock and we want to avoid that
But sometime it did work which confused us but I think we have identified the problem with the Proxy authentication
Our proxy requires full authetication against our Active Directory
So when it worked was just because we just before signing had been surfing on the internet and the proxy had cached the credential approvals
So when Adobe tried to get out to the timestamp server the ID was already authorized in the proxy
But without a previous "IE-surfing" it fails, the proxy has nothing in its cache
A network trace confirms this, we see a "Authentication required" request from the proxy that Acrobat never responds to
The proxy does not accept annonymous requests
IE is configured to use a configration script for its proxy settings
I cant find any relevant Acrobat settings that handles this and googling indicates that Acrobat has problems in this area
But I haven't found anything for our version/release
Now for the question, is Adobe Acrobat Standard 9.3.0 supposed to handle proxys that requires AD authentication?
To bypass the proxy is not an option
Setting a proxy exception for these servers is maybe an option
Prefered is that Acrobat handles this

To update my own question since it might help others
I received assistance through the Adobe support channels
Not what I was hoping for but it clarifies the problem
The reason I asked the question is that we don’t support Shared Review with an Authenticating Proxy server. So this customer workflow isn’t too far off the mark with having a proxy server authentication expectation in the standalone client and wanting a timestamp server time. The only workaround to this behavior is to do exactly what they have found. Launch an instance of Internet Explorer, authenticate against the proxy server and then sign the PDF file.

Problem after 9.2 / 8.17 updating - proxy authentication returns

We just updated to 9.2 and 8.1.7 of Acrobat and Adobe Reader on our SME network (Windows XP SP3 clients connected to Microsoft SBS2003 Premium server, so a typical SME setup).
When I then tried the usual [Check for Updates] I was unpleasantly surprised to see a previous problem appear - Acrobat and Adobe Reader both refused to connect to the internet without manual authentication to the Proxy Server (even when an admin account was logged in already). SBS2003 uses ISA as a proxy server, which works fine with all modern apps.
This was a major problem with Acrobat/Reader (and CS) until fairly recently when I assume the teams responded to complaints and modified the apps so that updates could occur without someone manually traipsing around client machines to enter authentication details.
Now we are back to square one - can someone please advise if this issue is 'accidental' (and hopefully therefore to soon be remedied) or if it was a deliberate move?
If the latter, I'd be interested to hear the justification behind it - it is making Reader in particular more trouble than it is worth to install.

Finally found another tread on this obscure problem -- I don't know why Adobe doesn't have a KB on this issue that their update causes.
I added *.adobe.com to the ISA server rules then the clients could run updater fine again.

Multiple proxy authentication prompts

When some particular sites are visited, multiple proxy authentication prompts are received. After canceling these pop-up windows the page can be finalized visited, we have observed that this issue is happening when Adobe Flash player is involved.
This has been an intermittent issue over the last months, however there is a site that can be used to reproduce the problem.
http://tv.adobe.com/watch/accessibility-adobe/preparing-indesign-files-for-accessibility/
Google chrome and IE are not affected

Hi Tylerdowner,
Thanks for your response. I should have mentioned two things, I am already using a recent firefox version (16.0.1) and these authentication prompts are for proxy user and password, these are not related with digital certificates as suggested in the first answer provided.
The problem that we are experiencing it is pretty similar to a well-known behaviour experienced in previous firefox versions. This can be replicated as follow:
0) Start firefox .
1) Open several sites in different tabs.
2) Close firefox selecting "Save and quit"
3) Start firefox again. Multiple authentication prompts (user and password) will be required.
Our current situation is pretty similar but it is happening when some sites with adobe flash player content is visited. For instance when this site is visited [[link text|http://tv.adobe.com/watch/accessibility-adobe/preparing-indesign-files-for-accessibility/ ]] multiple authentication prompts are poped-up
It seems to me (speculating) that adobe flash plugin may be sending a burst of hits through the proxy, as none of them has been previously authenticated, one username/password request is being sent to the browser one for each "hit" that was simultaneously sent through the proxy.
Thanks for your feedback.

My app store is not working after installing mavericks. When I open app store it repeatedly asking me to login with apple ID and to provide User name and Password for proxy authentication in a loop.I am a newbie to mac,Please help me.

My app store is not working after installing mavericks. When I open app store it repeatedly asking me to login with apple ID and to provide User name and Password for proxy authentication in a loop.I am a newbie to mac,Please help me.

Hmmmm... would appear that you need to be actually logged in to enable the additional menu features.
Have you tried deletting the plists for MAS?
This page might help you out...
http://www.macobserver.com/tmo/answers/how_to_identify_and_fix_problems_with_the _mac_app_store
Failing that, I will have to throw this back to the forum to see if anyone else can advise further.
Let me know how you get on?
Thanks.

Is there a script to add to a form in LiveCycle to disable digital stamp editing in Adobe Reader

I work for a state Agency and we want to use digital stamps as our signatures on our internal documents. I have created the form in LiveCycle and I know that in Adobe Reader by default the stamp will use the person's sign on ID for the stamp and then the person adds their name and other information.
However, if the person right clicks the stamp, and edits the Identity and puts in another sign on ID number, such as their supervisor's and stamps the document, there is no way to tell that both of those stamps, with different sign on IDs and names, were created by the same person.
If there is a script I can enter in LiveCycle, that when the form is opened in Adobe Reader, that would lock the Identity field of a stamp created in Adobe Reader from allowing a change to the sign on ID, then that would solve our problem and maybe the problem for other state agencies wanting to follow suit.
The digital signatures are even worse. I made one in my name, my supervisor's name and my dog's name, attached them all to a document, validated all the signatures and they look absolutely authentic. Why would Adobe make digital signatures like that? If we could just find some evidence within the data showing that all the signatures were applied by the same person or on the same computer, then we could use them. But the stamps at least grab that unique sign on number that we use and applies it to the stamp if the user doesn't alter it.
I'm on a time crunch as we hoped to launch this after the first of the year but our attorneys are saying, "uh, uh" until something can be done to prevent fraud. We have over 3,000 people in our agency so EchoSign would be out of the question.
I'd appreciate any suggestions.

Maybe some sort of "get identity" or something. We just need to be able to prove who put the stamp on the document.

Is there a way to force Adobe Reader to grab the sign on ID for a digital stamp?

I work for a state Agency and we want to use digital stamps as our signatures on our internal documents. I have created the form in LiveCycle and I know that in Adobe Reader by default the stamp will use the person's sign on ID for the stamp and then the person adds their name and other information.
However, if the person right clicks the stamp, and edits the Identity and puts in another sign on ID number, such as their supervisor's and stamps the document, there is no way to tell that both of those stamps, with different sign on IDs and names, were created by the same person.
If there is a script I can enter in LiveCycle, that when the form is opened in Adobe Reader, that would lock the Identity field of a stamp created in Adobe Reader from allowing a change to the sign on ID, then that would solve our problem and maybe the problem for other state agencies wanting to follow suit.
The digital signatures are even worse. I made one in my name, my supervisor's name and my dog's name, attached them all to a document, validated all the signatures and they look absolutely authentic. Why would Adobe make digital signatures like that? If we could just find some evidence within the data showing that all the signatures were applied by the same person or on the same computer, then we could use them. But the stamps at least grab that unique sign on number that we use and applies it to the stamp if the user doesn't alter it.
I'm on a time crunch as we hoped to launch this after the first of the year but our attorneys are saying, "uh, uh" until something can be done to prevent fraud. We have over 3,000 people in our agency so EchoSign would be out of the question.
I'd appreciate any suggestions.

You will not get what you need using stamps, especially if you ever want to use dynamic XFA forms.
The digital signatures that were signed with a self-signed digital ID won't fully validate unless the user chooses to trust the corresponding digital certificate first. You should only trust a digital certificate if you trust its source. The problem is using self-signed IDs will be difficult to use on the scale you're talking about.
Digital signatures are the best approach for your needs. They can provide both nonrepudiation of document origin as well as document integrity. You just have to figure out how to implement a solution you can afford.
You agency can become its own certificate authority and issue certificates to its employees. You'd just have to find a way to implement and manage such a system.

Adobe Reader 9 - proxy authentication

Similar Messages

Maybe you are looking for