|
>>
To answer Scott Cote: obviously the final implementation would be decided
in the JIG.
>>
But it would probably be based on the jabber network. So for instance, to
login to a
>>
website/service you would provide your Jabber network address ( i suggest
this as a
>>
more user friendly name JID ) and then your jabber server would be
contacted to authenticate. Ah, now I see. That makes perfect sense.
Thanks.
>> However, like I've said before, we should recognise that this is bigger than Jabber. If we >>
define a protocol, it should be sufficiently abstracted to allow bindings
to other protocols
>>
as well, therefore allowing interoperability.
Even
better.
-Scott
|
- [JDEV] Distributed Authentication - thoughts people? Michael Hearn
- Re: [JDEV] Distributed Authentication - thoughts p... Jonathan Siegle
- RE: [JDEV] Distributed Authentication - thoughts p... Scott Cote
- RE: [JDEV] Distributed Authentication - thoughts p... Peter Saint-Andre
- RE: [JDEV] Distributed Authentication - though... Peter Saint-Andre
- Re: [JDEV] Distributed Authentication - thoughts p... Gregor J. Rothfuss
- Re: [JDEV] Distributed Authentication - though... Jonathan Siegle
- RE: [JDEV] Distributed Authentication - thoughts p... Michael Hearn
- RE: [JDEV] Distributed Authentication - though... Jonathan Siegle
- Re: [JDEV] Distributed Authentication - though... Scott Cote
- Re: [JDEV] Distributed Authentication - though... Adam Theo
- Re: [JDEV] Distributed Authentication - though... Adam Theo
- RE: [JDEV] Distributed Authentication - thoughts p... Max Metral
- Re: [JDEV] Distributed Authentication - thoughts p... Jay Curry
- Re: [JDEV] Distributed Authentication - thoughts p... Stuart Dortenzio
- Re: [JDEV] Distributed Authentication - thoughts p... Adam Theo
- Re: [JDEV] Distributed Authentication - though... Michael Hearn
- Re: [JDEV] Distributed Authentication - th... Michael Hearn
- Re: [JDEV] Distributed Authentication - thoughts p... Peter Saint-Andre
