Creative Cloud & authenticating proxies?

This worked for me (h/t to my IT guy):

* add http://localhost:8092/ to exceptions in your brower's advanced settings.

We have a "solution", unfortunately it won't work for many/most. 

Our proxy is ForefrontTMG.   We have installed the ForefrontTMG client

onto workstations with CC apps.   The client handles authentication and

is transparent to the update application.

In the near future we will move to OpenDNS and stop using the proxy,

partly because of a number of misbehaving apps that are a pain to support.

I'm also about to start testing Adobe Remote Update Manager to get around
the local admin security issue.

Is there any plan to implement a proxyconfig or PAC file for use with Adobe Application Manager?

We allow all of the Adobe sites through are proxy, but the problem is that the actual Adobe Applications do not know how to "talk" to the proxy.

Please help!

Hi All,

as Adobe seems not really intending to fix this i want to share another workaround. it helped me today, not sure how long.

Our environment:

- McAfee WebProxy

- Cisco ASA Firewall (80, 443 not open to "any", but for some IP-adresses to overcome proxy issues)

- Proxy.Pac (wpad) File on a internal Webserver to tell clients to use the proxy for external websites

1. I have created a big list of FQDN and put them into Whitelist of the Proxy. => still issues as many others in this forums have

2. I checked one client using wireshark and netstat and the behaviour is very strange. most of the web-access goes (as expected) through the webserver. some websites (as soon i try to start adobe cc) are simply ignoring the proxy-setting and try to go through directly (which is blocked on the firewall)

3. unfortunately those destination adresses are changing and they have no common dns entry. most are listed as .amazonaws.com

So now to the workaround:

I have just opened the firewall for the IP 107.22.242.141 and FQDN helpexamples.com Port 80 and 443

No kidding - it worked since that.

No sure how stable this workaround is, we will see. Feel free try and comment

I'm sorry to be repeating myself, but I would ask that you raise a support ticket by visiting https://www.adobe.com/support/ regarding this. Please feel free to cite this thread and the details of your proxy server so that we can get this addressed by our engineering teams.

I hope this saves someone some of the aggravation that I have experienced with the incompetence at Adobe tech support.  This does not apply to all, but 96% of them earn this description.  If you have a firewall and/or proxy you will have authentication issues.  Creative Cloud for Teams has very little support for these devices.  I have spent weeks and hours talking to so called experts on the phone and chat sessions trying to figure out why my company has experienced problems accessing cloud services within these applications.  I FINALLY reached a 2nd tier tech, at least that is what he told me he was, and finally was told this little tidbit of information.  You would think that the 1st tier support would have this information or understand the mechanics of basic customer service and follow up on open tickets.  But no, they sit in a pending status of awaiting adobe response.  The tickets will remain in that status forever or be withdrawn by adobe without notice.  Pathetic.  Calls to the San Jose corporate office go into a black hole trying to escalate the problem. 

When talking to initial sales do you think they would have this information so that they could ask questions to make sure you purchased the appropriate bundle?  NO!!!

So we passed the 3 year anniversary of Adobe not fixing the problems outlined in this thread.  I have been assigned a "special" tech to address all of my concerns. While he has been polite and doing what he can under the circumstances the problem still exists.

Adobe does not care about it's customers in corporate environments that use firewalls and proxy devices.  If they did there would be more concern, and more choices available for us.

Their solution for me?  I was given a link to download pdf help files.  It is a 22 mb "book" for my users to use when they have problems.  I work with designers, they want non technical ways to find information.  Don't give me a textbook for them to use, and make me apologize for the crap Adobe has caused.  I'm so disgusted I could spit, and it isn't my money.  Luckily I have many contacts in the fashion industry, and when I can I will encourage them to find alternatives to the creative cloud.

You guys adobe support need to get your acts together.  This has been going on since 2012, and the last post is suggesting adding another layer of software that will probably violate a lot of corporate standards?  No admin is going to risk their job over the crap support given by adobe.  But as suggested here is my proxy information.  Barracuda firmware 8.0..0.003, these are the addresses listed in a custom folder assigned to authenticated users. 

ccmdls.adobe.com

ims-na1.adobelogin.com

ims-prod06.adobelogin.com

na1r.services.adobe.com

prod-rel-ffc-ccm.oobesaas.adobe.com

lm.licenses.adobe.com

ccmdl.adobe.com

swupmf.adobe.com

swupdl.adobe.com

.adobe.com

.adobelogin.com

.activate.com

Not working.  Fix it  My company is paying for 19 users which is probably not a lot compared to other organizations.  Adobe owes us some money.

At present, NTLM is unfortunately not supported as an authentication mechanism.

You may find more information using a software proxy such as Charles Web Debugging Proxy • HTTP Monitor / HTTP Proxy / HTTPS & SSL Proxy / Reverse Proxy which can be configured as an intermediary between your applications and a corporate proxy server.

If you are still seeing problems with this, please provide details of the software/hardware version of your proxy server and the type of authentication used (e.g. Kerberos, simple etc.).

Adobe, shame on you. Stop thinking that Creative Cloud users are single professionals connected to the internet with a 20 bucks soho router. In this world also exist low to mid to big companies who use web proxies (do you know? yeah, those hardware/software appliances which can filter web traffic, after user authentication). It's simply r-i-d-i-c-u-l-o-u-s that such a big company completely ignore all the complains on such a big issue (unable to authenticate with any web proxy) of the world's most famous graphic suite. WAKE UP, Adobe!!!