Please read before assuming this should go in another forum (like an android forum) - this is a Security question.
Here is the scenario:
Developing an health care based android application that has several "credential" elements that need to be stored and used during the application context. These are not the type of credentials where there is interaction with the user, in fact, all credentials are used silently in the background (user unaware) - so I can't go with the prompt each time method of "not storing credentials".
Android of course has the KeyChain class to rudimentary store credentials, but it is more oriented towards certificates and also involves some interaction to get credentials into (and possibly out of) the KeyChain, plus requires the device to become "passworded" (have a lock password... from what I can tell).
What I am looking for are ideas, advice, input, on how, in general application development, non-interactive credentials can be stored... and more specifically if you have some unique twist on the mobile/Android aspect that would be nice.
I have my ideas, but am looking to expand my mind here, to come up with the best solution I can. I will be writing a white paper on this, and if you are interested would be happy to post a link so anyone may access once I have completed my thoughts.
Thanks for all of the input ahead of time.