multiauth signin with multiple authentifications

[qMax]

If i got it correctly, MultiAuth does not allow user to use multiple
auth mechanisms to sign in.
But only to sign up.
Once registered, one has to use either native name/pass, or 3rdparty
scheme to login.

The code in tipfy.ext.auth.model.User:
auth_id = db.StringProperty(required=True)
Denotes single possible value for uth_id.

¿Is it ok to change this into
auth_id = db.StringListProperty(required=True)
So that users can create an account, and then login using any other
account _connected_ to their profile?

[Rodrigo Moraes]

On Nov 22, 8:41 pm, qMax wrote:
> The code in tipfy.ext.auth.model.User:
> auth_id = db.StringProperty(required=True)
> Denotes single possible value for uth_id.
>
> ¿Is it ok to change this into
> auth_id = db.StringListProperty(required=True)
> So that users can create an account, and then login using any other
> account _connected_ to their profile?

Hi,
Maybe I'm missing something, but how do you know that user logged in
using ThirdPartyAuth_1 is the same as the same user but now logged in
using ThirdPartyAuth_2? Leave it to users to create a solution to link
both accounts?

-- rodrigo

[qMax]

Yes. The task is more complicated then i thought.
However, from usability point of view, it looks very strange,
that a user signed up with third party, can not use native login.

I'm that user who implemented account relations through multiple
auth_ids in user model:
https://serial-experiments-qmax.googlecode.com/svn/tipfy-ext-polyauth/
Not much elegant, and not quite well working with sessions. But it
works.

For the moment, it is deployed here:
http://serial-experiments-qmax.appspot.com/

Also, it shows possibility of "guest signins" with @login_required,
mised in multiauth example.

Another idea could be leaving user_model as an account,
and then create additional model for user profile, and then link an
account to profile.
But that induces more entities and relations.

[pjesi]

I was looking for something similar. Correct me if this is already
implemented.

Basically you first sign in with either user+pass or a 3rd party
service. After that you should be able to connect additional services
(and create own user+pass if you didn't already). This makes it easier
for apps to interact with multiple services. Push data to Twitter and
Facebook for example.

Viðar

[qMax]

On 25 ноя, 04:36, pjesi <vidarsv...@gmail.com> wrote:
> Basically you first sign in with either user+pass or a 3rd party
> service. After that you should be able to connect additional services
> (and create own user+pass if you didn't already). This makes it easier
> for apps to interact with multiple services. Push data to Twitter and
> Facebook for example.

This is exactly what i've implemented.

With corrections, that "sign in" (=login) is just authentification, it
is ephemeral state somewhere in cookies/sessions.
And "sign up" (=register) is creating account in database, either
manually or automatically.
User may connect another auth-service to already existing eccount.

[Viðar Svansson]

Cool!

Will have a look at it soon, thanks :)

Viðar

> --
> You received this message because you are subscribed to the Google Groups "tipfy" group.
> To post to this group, send email to ti...@googlegroups.com.
> To unsubscribe from this group, send email to tipfy+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/tipfy?hl=en.
>
>

[Gabor Lenard]

This is exactly what I need. Thank you very much!

Do you think I can integrate it with Tipfy 1.0b1?

Gabor

[Lenard Gabor]

On Thu, Jun 16, 2011 at 07:21, Gabor Lenard <ga...@lenard.hu> wrote:

This is exactly what I need. Thank you very much!

Do you think I can integrate it with Tipfy 1.0b1?

 

Sorry, I was replying from Google Groups and it didn't quote the original message: