So far we've talked about accessing Google APIs, which use accounts and users defined by Google. If you have your own online service, though, it won't have Google accounts or users, so what do you do? It turns out to be relatively straightforward to install
new account types on a user's device. This lesson explains how to create a custom account type that works the same way as the built-in accounts do.
http://blog.csdn.net/sergeycao
Implement Your Custom Account Code
The first thing you'll need is a way to get credentials from the user. This may be as simple as a dialog box that asks for a name and a password. Or it may be a more exotic procedure like a one-time password or a biometric scan. Either way, it's your responsibility
to implement the code that:
- Collects credentials from the user
- Authenticates the credentials with the server
- Stores the credentials on the device
Typically all three of these requirements can be handled by one activity. We'll call this the authenticator activity.
Because they need to interact with the AccountManager
system, authenticator activities have certain requirements that normal activities don't. To make it easy to get things right, the Android framework supplies a base class,AccountAuthenticatorActivity
,
which you can extend to create your own custom authenticator.
How you address the first two requirements of an authenticator activity, credential collection and authentication, is completely up to you. (If there were only one way to do it, there'd be no need for "custom" account types, after all.) The third requirement
has a canonical, and rather simple, implementation:
final Account account = new Account(mUsername, your_account_type);
mAccountManager.addAccountExplicitly(account, mPassword, null);
Be Smart About Security!
It's important to understand that AccountManager
is not an encryption service or a keychain. It stores account credentials just as you pass them, inplain text. On most devices, this isn't a particular concern,
because it stores them in a database that is only accessible to root. But on a rooted device, the credentials would be readable by anyone withadb
access to the device.
With this in mind, you shouldn't pass the user's actual password to AccountManager.addAccountExplicitly()
. Instead, you should store a cryptographically secure token that would be of limited use to an attacker. If your user credentials
are protecting something valuable, you should carefully consider doing something similar.
Remember: When it comes to security code, follow the "Mythbusters" rule: don't try this at home! Consult a security professional before implementing any custom account code.
Now that the security disclaimers are out of the way, it's time to get back to work. You've already implemented the meat of your custom account code; what's left is plumbing.
Extend AbstractAccountAuthenticator
In order for the AccountManager
to work with your custom account code, you need a class that implements the interfaces thatAccountManager
expects. This class is the
authenticator class.
The easiest way to create an authenticator class is to extend AbstractAccountAuthenticator
and implement its abstract methods. If you've worked through the previous lessons, the abstract methods ofAbstractAccountAuthenticator
should look familiar: they're the opposite side of the methods you called in the previous lesson to get account information and authorization tokens.
Implementing an authenticator class properly requires a number of separate pieces of code. First,AbstractAccountAuthenticator
has seven abstract methods that you must override. Second, you need to add anintent filter
for "android.accounts.AccountAuthenticator"
to your application manifest (shown in the next section). Finally, you must supply two XML resources that define, among other things, the name of your custom account type and the icon that the system
will display next to accounts of this type.
You can find a step-by-step guide to implementing a successful authenticator class and the XML files in theAbstractAccountAuthenticator
documentation. There's also a sample implementation in theSampleSyncAdapter
sample app.
As you read through the SampleSyncAdapter code, you'll notice that several of the methods return an intent in a bundle. This is the same intent that will be used to launch your custom authenticator activity. If your authenticator activity needs any special
initialization parameters, you can attach them to the intent using Intent.putExtra()
.
Create an Authenticator Service
Now that you have an authenticator class, you need a place for it to live. Account authenticators need to be available to multiple applications and work in the background, so naturally they're required to run inside aService
.
We'll call this the authenticator service.
Your authenticator service can be very simple. All it needs to do is create an instance of your authenticator class inonCreate()
and call
getIBinder()
inonBind()
. The
SampleSyncAdapter contains a good example of an authenticator service.
Don't forget to add a <service>
tag to your manifest file and add an intent filter for the AccountAuthenticator intent and declare the account authenticator:
<service ...>
<intent-filter>
<action android:name="android.accounts.AccountAuthenticator" />
</intent-filter>
<meta-data android:name="android.accounts.AccountAuthenticator"
android:resource="@xml/authenticator" />
</service>
Distribute Your Service
You're done! The system now recognizes your account type, right alongside all the big name account types like "Google" and "Corporate." You can use theAccounts & Sync Settings page to add an account, and apps that ask for accounts of your
custom type will be able to enumerate and authenticate just as they would with any other account type.
Of course, all of this assumes that your account service is actually installed on the device. If only one app will ever access the service, then this isn't a big deal—just bundle the service in the app. But if you want your account service to be used by
more than one app, things get trickier. You don't want to bundle the service with all of your apps and have multiple copies of it taking up space on your user's device.
One solution is to place the service in one small, special-purpose APK. When an app wishes to use your custom account type, it can check the device to see if your custom account service is available. If not, it can direct the user to Google Play to download
the service. This may seem like a great deal of trouble at first, but compared with the alternative of re-entering credentials for every app that uses your custom account, it's refreshingly easy.
分享到:
相关推荐
Dojo - Creating a custom widget创建自定义小部件 https://blog.csdn.net/nmj2008/article/details/113554363 博客的配套代码
非常详细的配置Kubernetes1.3集群的官方文档
Oracle Solaris 11.1 Creatinga Custom Oracle Solaris11.1 Installation Image-32
Oracle Solaris 11.3 Creating a Custom Oracle Solaris 11.3 Installation Image-36
Oracle Solaris 11.2 Creating a Custom Oracle Solaris 11.2 Installation Image-32
Oracle Solaris 11 Creating a Custom Oracle Solaris11 Installation Image-28
NULL 博文链接:https://clongjava.iteye.com/blog/1317649
GDI.plus.Programming.Creating.Custom.Controls.Using.Csharp,不用多说了,英文版的。只要一分。
WorkFlow HOL实验 WF HOL(2) 创建自定义活动(Creating Custom Activties)
GDI+ Programming (source code) - Creating Custom Controls using C# Source Code
Symbian_OS_Creating_Custom_Controls_v1_0_zh_ch
Creating_Custom_Browser_Extensions_to_Hunt_Low_Hanging_Fruits 安全架构 网络安全 信息安全研究 解决方案 移动安全
Creating a Website The Missing Manual(4th) 英文epub 第4版 本资源转载自网络,如有侵权,请联系上传者或csdn删除 查看此书详细信息请在美国亚马逊官网搜索此书
windows powershell创建本地用户
ug1118-vivado-creating-packaging-custom-ip.pdf,官方文档
「云安全」Creating_Custom_Browser_Extensions_to_Hunt_Low_Hanging_Fruits - 云安全 访问管理 应用安全 安全实践 Linux 网络安全
Creating custom type instances in XAML 9 Creating a dependency property 15 Using an attached property 25 Creating an attached property 28 Accessing a static property from XAML 33 Creating a ...
Creating a bitmap object from a BMP file从位图文件中创建位图对象(6KB)
Enable smooth data flow and create futuristic UIs by creating flexible custom views Scale your apps with responsive and data intensive views Book Description To build great user interfaces for your ...
这个问题曾困扰了我一段时间,无意中看到了网上的一篇文章,看完后真是觉得惭愧啊!还是平时的粗心大意造成的啊!