Our customer has Single Sign On implementation with Shibboleth. that post assertion back to our server on cloud. it works properly in IE, Chrome, ... but always fail on Firefox recently.
The error is famous "The connection was reset", I searched lots of discussion about this error, and found a workaround by change Firefox security setting as following:
open the firefox, clear all the cookies and caches, then point to about:config
search and set both “security.ssl3.rsa_aes_128_sha” and “security.ssl3.rsa_aes_256_sha” to false (by double click these item in the about:config window)
After change above 2 security settings, the issue is solved in firefox, everything is ok. But we can't suggest our customer to change their Firefox security setting. I am wondering why above two items caused "The connection was reset" error, can we have a solution on our server or Shibboleth ID server?
Really appreciate any suggestion.
I just experienced the same problem but with SimpleSAMLPHP. The problem was only in firefox and only on the postback of the SAML Response.
For us the reason for the error was that out LB had a cap on how much data it allowed in the header. Firefox adds more header data than the other browsers and the SAML Response was big enough to reach the cap.
After changing the cap, everything works fine.
Related
My browsers keeps throwing me a 'login to website:80 - Your password will be sent unencrypted' popup when trying to access most websites, including Google.
I've checked my girlfriends computer and hers has started doing this too...
Very concerning, does anyone know why this is happening? I have googled but can't find this problem. No amount of refreshing, cache emptying seems to solve the issue. Happening in all browsers. Same looking popup (see below).
If I hit cancel i get a 401:
401 Unauthorized
Your client does not have permission to get URL /cgi-bin/index.asp from this server.
This is a half answer...
After resetting my router the issue has stopped.
It would be great if somebody could comment as to why this was happening.
I want to highlight an issue that I am encountering with video indexer. On my machine, whenever I try to login to video indexer ( either microsoft or gmail account), it shows me blank dashboard like the one below:
I have tried running it on other browsers and incognito as well (clearing browser cookies too). But nothing works on my machine. However, the same works fine when I log in through my other machine. Any help will be appreciated.
Make sure you try incognito mode without any browser plugins/extensions.
Can you open the browser console and see if you are getting any errors or network issues?
Looks like the GRAPH API is hitting a 401.
This is used to return the currently logged in user.
Since you are saying it is working in another machine fine.
The possibility I can think of is because of Conditional Access Policy(Location based mostly).
There could be some policies(for Security) that can be set at the tenant level which is making the Graph API to error out with 401.
The one machine is within the compliance (trusted network/vpn/domain joined etc.) where as the other one is not compliant. Hence the error.
I have an extension that has been working for almost 2 years now with out issue. I havent made any changes in about a year, but recently i started seeing some change in behavior.
I use the Webrequest APi to intercept navigations. During the callback for some websites i need to do some security evaluations async. When this happens I redirect to a local resource (html) as an interstatial page that tells the user what I am doing. Once complete based off the evaualtion the page is redirected where it should be. This is ussually very fast and has worked great for the last 2 years. Since the latest version of chrome things dont seem to work anymore for all cases.
If i intercept an address bar navigation. everything works as expected. The interstatial pops and everythings great. However. If i click on the same website as a link on a webpage. I get the "Blocked by Extension page". (what you would get if the nav was cancelled). I also noticed that my interstatial is showing up in the web history and if i click on it from my history page everything works.
It seems as if a bug might have been introduced by google?
Just wondering if anyone has seen this.
Thanks
We use DocuSign embedded sending feature. Basically we create envelope through API and then display to a sender an iFrame window with envelope sending view where he can do final configuration and click the send button.
Google is introducing a change from Chrome 80 that is well described
here:
https://blog.chromium.org/2019/10/developers-get-ready-for-new.html
and here: https://www.chromestatus.com/feature/5633521622188032
Long story short: Any cookie that requests SameSite=None but is not marked Secure will be rejected by Chrome starting from version 80.
Currently we can see that DocuSign is not ready for this change. We see warnings in console about same site cookie.
When we change Chrome experimental flags: "SameSiteby default cookies" and "Cookies without SameSite must be secure" to enabled (as it will be set in Chrome 80) the iFrame stops working completely.
The questions are:
Is DocuSign aware of the change introducing in Google Chrom v 80?
Is DocuSign planning to develope neccessary changes so the iFrame will be working?
When those changes will be delivered?
Thanks Rafal, we were not aware of this issue. We are going to take a look at Chrome 80 (which is releasing in a month) and see what the issues are and get back to you with a resolution soon.
Have you considered redirecting to DocuSign instead of using an iFrame? Redirecting is recommended.
I just turned on the Chrome experiments mentioned in the article you referenced and the Signing Ceremony worked fine when I redirected to it.
I need some advice on setting up merchant account in google.
When I try to set up merchant account, account signing up page shows me an error.
The error code is shown as "An error occurred {"type":"PLATFORM_ERROR", "payload":"0"}"
I've tried to resolve this issue with Google support team, but they keep sending me general information and manual..
Please give me suggestions on this issue. (I already finished developing my commercial application, but can't set the price because of this issue. )
Thanks in advance.
I had the same issue.
What I did to resolve it was to flush the browser cookies, history and cache. After that, I opened a new browser tab and logged in to my Google Wallet account (the one I set up previously to BUY apps on the play store). As I was logging in, I noticed there was some error but it quickly resolved itself - I successfully logged in and could see what I previously bought.
After that, I closed and re-opened my Google Dev Console, and tried to setup a Merchant Account again and it worked.
I experienced the same problem and I finish solved changing my address length, uou can't use more than 64 characters. see https://stackoverflow.com/a/21412790/2359141
clear cache and everything by using ctl+alt+delete
keep only one tab
Select proper product type , I selected Computer software its worked for me
Do sign out and login in wallet google
I found the solution.
You just have to let the VAT number empty during registration, fill it later.
It worked for me.
I got the payload error as well, what resolved my problem was changing my PO Box address to a physical address. Google chat support figured it out.