Notification.permission is set to denied and not present in blocked - push-notification

On my localhost in chrome during unit testing of Notification permission, I have closed the browser native notification permission box by clicking on (x)
after that I am not able to change / remove it to default from browser Setting > Content Settings > Notifications
localhost is not visible in blocked list, but when I check on console in chrome Notification.permission value is set to "denied"
Please help!

You just need to close and reopen the browser.
You can find the permission in the browser settings only if you click "Block" or "Allow". If you click "X" you deny permission only temporary.
In any case you can also check / change the preferences for a website by clicking on the lock icon near the address bar.

Related

Getting Correlation failed exception while signing in the auth0 inside an iframe

I can successfully login with the standalone mvc app without the iframe. But when I put the same app inside an iframe, I'm getting the Exception: Correlation failed exception.
When I tried with postman, I'm getting the following response:
I have also tried with different SameSiteMode configurations but to no avail. Is there any way or workaround to achieve this? Thanks.
I suspect the cookie is not sent by the browser.
You need to use HTTPS to get it to work together with samesite=none;Secure attributes added to the cookie. Otherwise the cookie will be blocked by the browser.
You can diagnose why a cookie was not accepted or used by going to the Chrome devtools and:
Open the Browser Developer Tools (F12)
Click on the network tab and reload the page
Click on the Cookies request
Select the Cookies tab
Then hover your mouse over the (i) to see the reasoning by the browser

iis two domain with ssl cert error browsing webpage

I have iis 10.0 which host two domains ssl cert, say 1 is www.abc.com and the another is www.dfg.com, both domain are pointing to the same iis. So I can access webpage like https://www.rgx.com/calculation.aspx and
https://www.dfg.com/calculation.aspx both. The problem is that for most page, both domain work properply, but for some webpage in one domain e.g dfg.com https://www.dfg.com/questions.aspx, it cannot be loaded, in firefox, it returns
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
So what is the reason that some page cannot be accessed in one domain but can in another domain?
Do you have an error code? This error seems to only appear in Firefox, try the following in Firefox to see if it resolves the issue on your end:
Open about:preferences#privacy in the browser.
Scroll down to the Certificates section and click on "View certificates".
Make sure the Authorities tab is selected.
Locate Avast certificates and use the delete option to remove them.
Use the import button to import the certificates from C:\ProgramData\AVAST Software\Avast\wscert.dat.

Force HTTPS on alfresco

I have been trying to enable HTTPS login on alfresco but it seems to be a challenge to get it working.
I can access my website via HTTPS and get the login page, but when I login with the correct credentials I get the following error :
Something's wrong with this page...
We may have hit an error or something might have been removed or deleted, so check that the URL is correct.
Alternatively you might not have permission to view the page (it could be on a private site) or there could have been an internal error. Try checking with your IT team.
If you're trying to get to your home page and it's no longer available you should change it by clicking your name on the toolbar.
I must login in HTTP then refresh my HTTPS page to be connected in HTTPS.
I have already seen what the offical doc says and tested it but it didn't work.
Has anyone an idea on how to fix the problem ?
Thanks
The alfresco.log / catalina.out should tell your more.
Where / how did you set up https? Have a a reverse proxy like nginx or apache in front of the alfresco tomcat?
If the log says something like "CSRF Token Filter issue" then you need to set share.host / port / protocol in alfresco-global.properties as seen from the browser.

Why would Facebook oauth try to access the http version of an https site?

When I try to use Facebook login on this site:
https://parlay.io
by clicking the button at the top of the page, I get a popup with the URL:
https://www.facebook.com/login.php?skip_api_login=1&api_key=501604519940587&signed_next=1&next=https://www.facebook.com/v2.2/dialog/oauth?redirect_uri=https%3A%2F%2Fparlay.io%2F_oauth%2Ffacebook%3Fclose&display=popup&state=eyJsb2dpblN0eWxlIjoicG9wdXAiLCJjcmVkZW50aWFsVG9rZW4iOiJxd01acHRSb3hGX0hDM1FEV25vSVVSVXlDZTZWcWVFNUhrUHZVcHA5ZWhUIiwiaXNDb3Jkb3ZhIjpmYWxzZX0%3D&scope=email%2Cuser_friends&client_id=501604519940587&ret=login&cancel_url=https://parlay.io/_oauth/facebook?close&error=access_denied&error_code=200&error_description=Permissions+error&error_reason=user_denied&state=eyJsb2dpblN0eWxlIjoicG9wdXAiLCJjcmVkZW50aWFsVG9rZW4iOiJxd01acHRSb3hGX0hDM1FEV25vSVVSVXlDZTZWcWVFNUhrUHZVcHA5ZWhUIiwiaXNDb3Jkb3ZhIjpmYWxzZX0%3D#=&display=popup
I enter in my Facebook creds and submit. In Safari, this works and login completes. In Chrome, the popup goes blank but stays open. The popup URL is
https://parlay.io/_oauth/facebook?close&code=...
The popup console says:
Uncaught SecurityError: Blocked a frame with origin "https://parlay.io" from accessing a frame with origin "http://parlay.io". The frame requesting access has a protocol of "https", the frame being accessed has a protocol of "http". Protocols must match.
The error occurs on line 23:
I don't know why this popup is trying to access http://parlay.io. I do not have http or http://parlay.io as a setting anywhere in my app.
This is using the 'popup' style oauth. When I switch to 'redirect' style in Chrome, the first time I login, I get this error on the server:
{"line":"398","file":"oauth_server.js","message":"Error in OAuth Server: redirectUrl (http://parlay.io/) is not on the same host as the app (https://parlay.io/)","time":{"$date":1435164688847},"level":"warn"}[parlay.io]
and I get redirected to same signin page. The second time I click login, it works. The second click can be automated with:
I had the exact same problem, under similar conditions (Meteor 1.3.x, ROOT_URL set to https, FB/Twitter apps set to https.)
What fixed the problem for me was to set up my site to always redirect HTTP requests to HTTPS. I am using Cloudflare, so I followed the instructions here:
https://support.cloudflare.com/hc/en-us/articles/200170536-How-do-I-redirect-all-visitors-to-HTTPS-SSL-
After making the change, sign-in worked like a charm across different machines. Final results here:
https://goodbyegunstocks.com

need to login 2 times

In my Drupal installation I often need to login 2 times to get logged in.
This is the case when I go exactly this way:
open a new incognito window in browser (in my case Chrome)
try to login -> login failed with no message
try to login 2nd time -> logged in
close the window WITHOUT logout
open a new incognito window in browser and try to login -> login failed
When I logout and try to re-login, the login works.
There are some more randomly cases where the login doesn't work too at the first time. But these cases I can't describe exactly.
In Drupal log and Apache log I don't get any message after a failed login.
Where can I start my search to solve this? Or does anyone had the same problem?
The session cookies are stored by drupal to confirm users as being logged in. Check the developer tools in chrome to asses whether a cookie has been or was meant to be stored. Icognito Mode makes a point of treating cookies with deference (might also be the general settings of your browser).
Try setting your cookie domain settings.php. Depending on your hosting or setup this sometimes needs to be done to make sure cookies are working correctly.
Basically you will add a line like
$cookie_domain = '.my_site.com';
Do not add a trailing slash and do not remove the leading period (this is documented and commented out in settings.php, do a find for $cookie_domain and you should see it.
https://drupal.org/node/1844574

Resources