no matter what I am doing(new account, new site, new app), its not saving any settings. That means I can't add a domain to the whitelist and also, I can't get a public key.
Their own site's Javascript is extreme messy and crashes all over the place. I guess they won't fix all this any time soon. I tried to reach them multiple times through their contact page, but as expected : no response.
I am wondering this is happening only to me. Can anyone confirm this ?
No I am facing the problem of receiving the data at all. I tried JSONP, JSON-REST over a proxy and some other things. When using JSONP without the api key (not the public), I am getting a HTTP 400 error.
Are there any alternatives to receiving the data through their API ? I can't use server side solutions.
well, any hints welcome.
thanks
This sounds like a bug, and you should definitely contact us with your shortname and the browser you're using: http://disqus.com/support/
Related
I'm working on a problem at the moment in which I need to authenticate a user of a desktop application with a oauth solution.
I know I could implement a solution where I redirect a browser on the authentication server, ask for creds then redirect to the resource to pull the data.
But, if I didn't want to actually use an external browser, is it possible to mimic the browser flow using just JS? In other words could I handle the redirects within JavaScript to finally achieve the token and next the data.
I haven't started the project just yet so this is kind of a feeling out question to see if the above is possible.
Just a small bit of info about the application. It's an Electron application. I have seen some examples for electron online but theses all use the external browser to achieve this.
I'm totally new to this type of work so any pointers in the right direction or help would be great.
And as I'm new to this type of work, apologies if it is a dumb question
Thanks for any help
I'm making a chrome extension where I want to create a security method for my chrome extension to stop it from getting shared without me in the process
I have an idea to generate a token somewhere (usually some backend, maybe server of the website that gets user registrations/payments my website which I am building with worpress), send token via email, get email+token in extension, make a request to the webserver to verify that they're valid. This seems like a typical auth flow except the password is now the token, which is generated instead of the set by the user. In other news, I have more ideas (Extension-side prng with shared seed, can check to see if the token is within X generations for eg.)
I want to be able to sell tokens on my website which only allow one user to prevent the token from being shared.
I tried to setup the Auth0 for the chrome extension but I keep getting errors and the process doesn't lead to how I would want to be done.
youtu.be/D0M1wid1L3Q?t=353
youtu.be/D0M1wid1L3Q?t=418
is a great example of what I want to be able to do. Can anyone help me doing this? I am building my website in wordpress not hard coding it so I'm not sure on How to do this exactly
If anyone can point me in a direction of what I am supposed to do or maybe provide some code that could help me?
I tried to
npm install auth
and put that in my manifest.json bit it doesn't work and it seems as if it doesn't do what I want.
I have found this url which might get me heading in the right direction:
https://auth0.com/docs/api-auth/tutorials/authorization-code-grant
I really appreciate the help.
So I'm working with the new node MVC framework Sails.js (https://github.com/balderdashy/sails) and I'm getting a weird error I've never had before. I'm trying to implement the example passport.js authentication strategy (https://gist.github.com/theangryangel/5060446) Sails.js includes in the documentation, but when I try to access my homepage (http://localhost:1337/) while not logged in I get routed to http://localhost:1337/login but it doesn't load and chrome gives me this error:
This webpage has a redirect loop
The webpage at http://localhost:1337/login has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.
Here are some suggestions:
Reload this webpage later.
Learn more about this problem.
Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects.
Does anyone know what's going on?
looks like that message is coming from Passport. Hop in the IRC (#sailsjs) if you want and we can take a look. In the mean time, #robertklep's suggestion seems like a strong possibility to me.
I'm writing a web app, and I have the classic problem that the session cookie is shared between browser instances, and browser tabs. Obviously the browser doesn't send back anything the header. However I am able to control all the requests inside the app, so I'm wondering if I can add my own "parameter".
So the question is, is there some JavaScript which might identify the process ID, or Instance ID, or Tab ID on the client side? I can take care of sending it to the server, but I'm wondering if anyone knows of any tricks on the browser side.
Browser-specific suggestions are welcome - I'm very happy with answers that will only work in one browser type.
Here is the list of information you can get from javascript: Information about your Web Browser from Javascript. I don't think you can get system specific information like PIDs from javascript, it would certainly be a security issue.
sessionStorage might help you here.
http://www.nczonline.net/blog/2009/07/21/introduction-to-sessionstorage/
update:
window.name can be used.
I've been trying to solve a Javascript problem on my company's site that a single user has reported, but have exhausted all possible fixes I can think of. To do more, I'll need more information about what's happening in the user's browser. Can anyone suggest a bookmarklet or other tool I can send to this user to print a log of all Ajax calls and exceptions raised, so the user can send it back to me?
I ended up using Firebug Lite. An automated system that could send me the information directly would have been better, of course, but there wasn't time to set that up. Thanks for the suggestions!
Log all the information you want in a cookie and have the customer send the cookie back to you.
There are a few framework for logging to the browser console in JS, log4Javascript is the one I've used and had good luck with. Alternately, you could send back relevant log information in an AJAX call to a server-side script that writes out a client log and the customer wouldn't have to mess around with sending logs or cookies.
A try-catch block around the "suspect" part of your code.
- and some form of submit in the catch-part, sending details of the incident back to the server - eg. via a form-submit in a hidden iframe or Ajax..