By default it _does_ keep some minimal data, mostly around the token (used for making authenticated calls to the remote service). Exactly what it stores depends on the specific service, but generally it falls within the following list:
– user id
– username
– actual name (first/last)
– profile picture
That being said, if you wanted to, you could very easily just delete the token as soon as you’d verified/logged them in (there’s a method to do that– $this->store->delete( array( 'id' => $id ) ).
Also note that the way this plugin is set up is really targeted at connecting accounts for existing users of the local WordPress install, so you’d probably have to jump through some hoops to make things work for “non-users” (visitors).
HTH
Thread Starter
asbell
(@asbell)
Hi Beau. Any way I could speak with you via phone/Whatsapp/Skype? Iwant to talk about extending or substituting the Authentication mechanism to go to my CRM to get credentials via its api. My phone etc is at http://www.propertyunderthepalms.com
Sorry, I don’t do consulting work currently, and that sounds well beyond basic/central support for Keyring. You might be able to find someone who can help you via somewhere like https://jetpack.pro.
Thread Starter
asbell
(@asbell)
Gosh Beau. I have gotten the same response from most people and the ones who everyone refers to me do not have the expertise in Authentication to know how to answer. Forget about consulting…this may be a money making plugin capability which your product can address. Can we just speak briefly and brainstorm for a few minutes?
