I would like to emphasize the earlier point….it would be nice if we had a
solution that did NOT require an interactive browser procedure.
Randy
On Sep 17, 2012, at 5:21 PM, Randy Turner wrote:
> What about a combination...OpenID Connect ?
> Peter Saint-Andre wrote:
> -BEGIN PGP SIGNED
What about a combination...OpenID Connect ? Peter Saint-Andre
wrote:-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/17/12 3:00 PM, Ivan Martinez wrote:
> I'm currently considering wether to use OAuth2 or OpenID2 in my
> server. Which one do you think will be more adopted as a user
> authentic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/17/12 3:00 PM, Ivan Martinez wrote:
> I'm currently considering wether to use OAuth2 or OpenID2 in my
> server. Which one do you think will be more adopted as a user
> authentication mechanism in XMPP servers?. Which companies are
> planing to use
I'm currently considering wether to use OAuth2 or OpenID2 in my server.
Which one do you think will be more adopted as a user authentication
mechanism in XMPP servers?. Which companies are planing to use each of
them?.
Thanks,
Ivan
On Mon, 17 Sep 2012 13:39:46 -0600, Peter Saint-Andre wrote:
While searching for the design guideline that says "don't put big things
inside a presence stanza, use PEP" I found XEP-0134 and it almost had
what I was looking for:
Finally, as explained in XMPP Core, the stanza exists to
broadcast network and communications availability only; for more
adva
On Monday, September 17, 2012 01:39:46 PM Peter Saint-Andre wrote:
> On 9/17/12 1:36 PM, Ralph Meijer wrote:
> > On 2012-09-17 21:10, Randy Turner wrote:
> >> PLAIN is going to be deprecated, even though TLS is pretty much
> >> ubiquitous?
> >
> > This has to do with their intent to ban the use of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As author of XEP-0281, I have changed its state from Deferred to
Retracted, since I now favor XEP-0289 instead. Just FYI.
Peter
- --
Peter Saint-Andre
https://stpeter.im/
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Commen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/17/12 1:36 PM, Ralph Meijer wrote:
> On 2012-09-17 21:10, Randy Turner wrote:
>> PLAIN is going to be deprecated, even though TLS is pretty much
>> ubiquitous?
>
> This has to do with their intent to ban the use of passwords in
> applications a
On 2012-09-17T21:10:20 CEST, Randy Turner wrote:
> PLAIN is going to be deprecated, even though TLS is pretty much
> ubiquitous?
Looks like it only affects GTalk.
--
Regards,
Kim "Zash" Alvefur
signature.asc
Description: OpenPGP digital signature
On 2012-09-17 21:10, Randy Turner wrote:
PLAIN is going to be deprecated, even though TLS is pretty much ubiquitous?
This has to do with their intent to ban the use of passwords in
applications and rely on 2-step verification with OAuth2 bearer tokens.
--
ralphm
PLAIN is going to be deprecated, even though TLS is pretty much ubiquitous?
RandyRalph Meijer wrote:On 2012-09-13 19:20, Peter Saint-Andre
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 9/11/12 4:24 PM, Lance Stout wrote:
>> It's a bit annoying that they add an extra attribute t
On 2012-09-13 19:20, Peter Saint-Andre wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/11/12 4:24 PM, Lance Stout wrote:
It's a bit annoying that they add an extra attribute to the element, because it adds a special case to check in what would
ideally be a fully generic implementatio
12 matches
Mail list logo