![]() Please see the sample plugin “PluginA” in the KP2A repository for a simple example on how to do this: ![]() In addition, it is even possible to add new fields or modify existing fields. This is done, for example, by the QR plugin ( ). You can add menu options for the full entry or for individual fields of the entry when displayed to the user. These strings will be displayed to the user when KP2A asks if access should be granted. The Great PluginA Test plugin to demonstrate how plugins work (your-name-here) To tell Kp2a that you’re a plug-in, you need to add a simple BroadcastReceiver like this: As not every app/plug-in requires access to all information, you must specify which scopes are required by your app. Before your app/plug-in gets any information from KP2A, the user will have to grant your app/plug-in access to KP2A. Keepass2Android stores very sensitive user data and therefore implements a plug-in authorization scheme based on broadcasts sent between the plug-in and the host app (=Keepass2Android or Keepass2Android Offline). Now add a reference to the PluginSDK library from your existing app or add a new plug-in app and then add the reference. You should be able to build this library project. Preparationsįirst check out the source code and import the Keepass2AndroidPluginSDK from into your workspace. In case you have any questions, please contact me. Please follow the steps below to get started. How to create a plug-in or connect from your appĬreating a plug-in for Keepass2Android or enabling your app to query credentials from Keepass2Android is pretty simple.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |