Sharing a custom AccountAuthenticator between applications

I have an application that I created for a client that uses its own AccountAuthenticator. It works great and it does what the client wants.

However, this is only the first application in what will be a set of applications that will use the same authentication manager, and it is here that I am not sure how to proceed.

I have no way to find out which applications will be installed by any user or how to install them. I do not want the user to provide their credentials for each application; which defeats the goal of having an authentication manager.

From some initial testing, it seems that including the same code in every application will not work.

Do I have to do something like what is needed to use any Google Play services? Write a function that checks for the existence of an application that simply performs authentication, and then sends the user to the market to install an application that performs authentication? Or download apk from our own servers?

Or is there another way to avoid having to push the user out of the application?

+4
source share
1 answer

I am trying to implement the same environment as you, several applications using the same account, my last approach (I am not saying this in the best way):

"" -, , , Google .

- , AccountManager ( ), , .

-, (. )

0

All Articles