"Authentication failed" when I click on the "likes" and "accept as solution" buttons

[owenwqp1]

Hi everyone, Anytime I click on the "likes" and "accept as solution" buttons, the following message appears: Authentication failed for the action you are trying to do. This failure could be due to your browser not supporting JavaScript, JavaScript not being enabled, or trying to use the action URL directly in the browser address bar instead of clicking the link on the page. Return to the original page. How could I solve this problem? I feel very much ashamed because I could not tell the others my problem solved with the help of members in the community. Thanks a lot!

[RW9]

Yes, this authentication server bit is a real pain.  I find I get this when on one tab I have done an operation where it signs me in, and then on another I click like and it can't sign me in.  In the top right you should see a sign in button (or your username).  Click the signin button and signin, then navigate using that tab to the place where you want to add likes and mark as solution.  If it still doesn't work, and it shows your username in the top right, then this may need to go to Chris to have a look at.

[Kurt_Bremser]

Chris = @ChrisHemedinger

[ChrisHemedinger]

Thanks for being diligent about Liking and Accepting Solutions, @owenwqp1! Try the steps @RW9 mentioned and if you continue to have problems, let me know.

[owenwqp1]

Hi Chris, I still have problem with the "likes" and ''accept as solution" button. Could you give more suggestions? Thanks!

[ChrisHemedinger]

I see that you're in China.  Any chance that some content is blocked from you location / ISP?  This might prevent the proper running of the scripts. 

And are you seeing this when clicking in the web browser, or are you clicking the "like" and "accept solution" links in the e-mail notifications that you might receive?

[owenwqp1]

Hi Chris, I see the message when I click on the "likes" and "accept as solution" button, not the links in the e-mail notifications. Thanks!

[ChrisHemedinger]

Okay, one more request for info.  Can you open the developer console (usually F12 in your browser), refresh the page, and share the messages that you see in the developer console?

If you have messages in there, please copy and paste (as text) into a reply.

[owenwqp1]

Access to Font at 'https://www.sas.com/includes/fonts/an/b4199f62-4009-46e6-9359-5c262251c962.woff' from origin 'https://communities.sas.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://communities.sas.com' is therefore not allowed access. false#M104911:1 Access to Font at 'https://www.sas.com/etc/designs/core/font/sasicons-072717.ttf' from origin 'https://communities.sas.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://communities.sas.com' is therefore not allowed access. false#M104911:1 Access to Font at 'https://www.sas.com/includes/fonts/an/bb495831-ebf7-4423-9a14-ee11bf6b292f.woff' from origin 'https://communities.sas.com' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header has a value 'https://www.sas.com' that is not equal to the supplied origin. Origin 'https://communities.sas.com' is therefore not allowed access. https://www.google.com/ads/ga-audiences?v=1&aip=1&t=sr&_r=4&tid=UA-1022528-1&cid=952343986.151195277... Failed to load resource: net::ERR_CONNECTION_REFUSED https://ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js Failed to load resource: net::ERR_CONNECTION_RESET false:12107 Uncaught TypeError: $ is not a function at false:12107 https://platform.twitter.com/oct.js Failed to load resource: net::ERR_CONNECTION_TIMED_OUT satellite-566842cf64746d54aa002f76.html:44 Uncaught ReferenceError: twttr is not defined at satellite-566842cf64746d54aa002f76.html:44 satellite-566842cf64746d54aa002f76.html:53 Uncaught ReferenceError: twttr is not defined at satellite-566842cf64746d54aa002f76.html:53

[ChrisHemedinger · Accepted solution]

Hi @owenwqp1 - it looks like one of our site components was referencing a Javascript library hosted at google.com, which could be a problem for visitors from China.  I've made a change to use the built-in version of the library that we have.  I hope.

Use Shift+f5 to force-refresh the site when you visit, and see if this helps.  And I'm hoping it has no detrimental effects -- in my testing things seemed to work okay.

Chris

[owenwqp1]

@ChrisHemedinger

Thank you so much Chris,the problem solved.

Cheers,

Owen