#1

I am currently offering “Product A” with Sign in with Twitter login authentication.
We would like to integrate user data(database) of “Product A” and “Product B” services.

Once we integrate the user data, we can use the following.

User can login to Product A with Sign in with Twitter login authentication
Also user can login to Product B with the same authentication token.

Is the above behavior allowed by the Sign in with Twitter login authentication service?

#2

Different twitter apps will always generate different tokens, even for the same user, and tokens generated for one app cannot be used with a different app.

However - if you’re only using a single twitter app to log in, and you’re handling “Product A” and “Product B” logins yourself it’s entirely up to you how you do that. You can add multiple callback URLs to an App, so if you use one twitter App as the “Login with twitter” app for both “products” it would work (provided you code the rest of it)

1 Like
#3

thank you for answering my questions.
now I understood the behavior.

but I also have a question.
in terms of twitter policy. it is OK if we integrate user data(database) then twitter token use for 2 product?

#4

That’s probably something to ask twitter on Platform or in the Rules and Policies - Twitter Developers section for someone from twitter to answer that. But generally avoid these: More on restricted use cases – Twitter Developers | Twitter Developer Platform

1 Like
#5

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.