I am trying to implement oauth login to latest huggle, however I am
confused about several things:
1) How do I obtain the data which are normally provided in a callback URL?
2) What is consumer key and secret? Can these values be shown to
end-users? Do these values need to be known by
On Thu, 12 Sep 2013, at 11:13, Rodrigo Padula wrote:
Hello Guys,
and for Firefox users, you can try FirefoxOS through the simulator
extension.
https://addons.mozilla.org/pt-br/firefox/addon/firefox-os-simulator/ ;-)
Remember that your app may need to be multilingual. The simulator
Don't know the answer to 1 but,
On Thu, Sep 12, 2013 at 5:57 AM, Petr Bena benap...@gmail.com wrote:
2) What is consumer key and secret? Can these values be shown to
end-users? Do these values need to be known by application itself? If
consumer secret is supposed to be known by application
Ok, so should we ask users for password then? Is that the only
alternative in the moment?
On Thu, Sep 12, 2013 at 12:57 PM, Tyler Romeo tylerro...@gmail.com wrote:
Don't know the answer to 1 but,
On Thu, Sep 12, 2013 at 5:57 AM, Petr Bena benap...@gmail.com wrote:
2) What is consumer key and
On Thu, Sep 12, 2013 at 8:41 AM, Petr Bena benap...@gmail.com wrote:
Ok, so should we ask users for password then? Is that the only
alternative in the moment?
Pretty much, unless Chris has a better recommended solution.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major
Hi Petr,
Unfortunately, you're trying to do two things that the version of oauth we
implemented doesn't do very well. OAuth 1 enabled users on website A to
safely grant website A access to specific resources on website B. Any other
use, you have to be very careful to ensure that the the protocol
Le 12/09/13 08:53, Brion Vibber a écrit :
And the job queue should be completely redone so it's not awful, if we
haven't started on that already. :)
I would love us to be able to rely on a job scheduling system such as
Gearman (http://gearman.org/), there are most probably other around.
On Thu, Sep 12, 2013 at 2:57 AM, Petr Bena benap...@gmail.com wrote:
I am trying to implement oauth login to latest huggle, however I am
confused about several things:
1) How do I obtain the data which are normally provided in a callback URL?
If your app doesn't have a sensible callback URL,
On Thu, Sep 12, 2013 at 12:00 PM, Brad Jorsch (Anomie)
bjor...@wikimedia.org wrote:
I'm personally still not clear on how OAuth 2 solves this problem,
unless it's just by saying you must use HTTPS, and don't assume that
the consumer secret is really secret. Which we could well enough do
with
Sounds cool. When is it going to be available for developers on production?
On Thu, Sep 12, 2013 at 8:03 PM, Tyler Romeo tylerro...@gmail.com wrote:
On Thu, Sep 12, 2013 at 12:00 PM, Brad Jorsch (Anomie)
bjor...@wikimedia.org wrote:
I'm personally still not clear on how OAuth 2 solves this
All the documentation I could find is in docs/deferred.txt. Let me
paste the paragraph:
A few of the database updates required by various functions here can be
deferred until after the result page is displayed to the user. For example,
updating the view counts, updating the linked-to tables
if you have a moment, the following change sets are ready for review:
* https://gerrit.wikimedia.org/r/#/c/83657/
* https://gerrit.wikimedia.org/r/#/c/82619/
https://commons.wikimedia.org/wiki/Commons:GLAMToolset_project
___
Wikitech-l mailing list
12 matches
Mail list logo
