P3KI Core can be understood as a mandate system.
You give a precise permission to Party A, Party A can delegate some or all of this on to Party B. Which is called "delegating" a permission.
Party B can now access a device or service you control by presenting their mandate (you-to-A, A-to-B) and prove their identity (they are really B).
This works without active involvement from you or A at the time of verification.
Yes.
We offer a mobile app for Android.
iOS and other platforms are coming soon.
Yes.
Please talk to us regarding platform details and space / memory requirements.
Yes.
We offer a RESTful daemon implementation that is easy to integrate.
Yes!
It's one of our key features!
No!
P3KI delegations are personalized and traceable to individual identities, even if some or all are further delegated.
It's fully auditable and traceable.
It's a full or partial, precise granting of a permission, role, or capability to a party.
Yes, if X calls for authorization and/or authentication of one device to another for a very specific access permission that can be even scenario dependent.
No.
P3KI Core is fully storage agnostic, so you are free to store data in the Blockchain or use data read from the Blockchain. However, we do not rely on Blockchain technology in any way.
If you're asking because us saying Blockchain is the only way you're going to do the right thing and talk to us, the answer is yes, of course, it's Blockchain.
Yes.
We offer integrations and bridges (proxies) for various industry standard interfaces.
We've so far successfully interfaced with Active Directory, Linux PAM, OAuth2, and a wide range of custom applications.
P3KI permission delegations are rescinded by simply no longer delegating to a given party anymore.
No!
This is one of the core principles behind how our permission model works.
Intermediate "Certificate Authorities" (there's really no such thing with P3KI, but bear with us here) can change the scope of permissions they delegate effectively on a minute-by-minute basis without you having to roll out new "client certificates" (another thing that doesn't really exist with P3KI's model).
This makes running a P3KI-based authentication and authorization solution significantly more cost effective than classic certificate authority approaches.
Permissions, roles, and capabilities are expressed using P3KI's Trust Policy Language (TPL).
TPLs can handle complex, multi dimensional expressions made up of several individual parts (aspects).
Individual aspects can have expressions with arbitrary precision.
Yes.
We recommend you closely follow documentation and consult with us.
Yes.
A hierarchy is a tree, and trees are strictly less powerful than full-featured graph networks (which P3KI's web-of-trust is).
This means you can fully use hierarchical models as well as web-of-trust models.
Yes.
That's one of the core concepts of P3KI.
Yes.
Any data store can be used with P3KI.
Yes.
Via the "pinning" concept delegations can be made that are tied to a specific identity.