forked from Mirrors/keyoxide-web
14 lines
1,012 B
Markdown
14 lines
1,012 B
Markdown
|
# Are you a service provider?
|
||
|
|
|
||
|
|
If you have:
|
||
|
|
|
||
|
|
* a website that allows users to create accounts
|
||
|
|
* a messaging platform
|
||
|
|
* any other type of service that may require users to prove their online identity
|
||
|
|
|
||
|
|
Then you may be interested in supporting decentralized identity proofs as they allow your users to securely prove their identity across services. Take a look at this [example](guides/service-provider) to find out how two persons can gain more confidence in knowing they are talking to and interacting with the right person in an online world where impersonating is all too easy.
|
||
|
|
|
||
|
|
The internet could be a slightly safer place if your service allowed your users to prove their identity. All the service needs to do is make a JSON file available with basic details about the user and set the correct CORS headers.
|
||
|
|
|
||
|
|
The [documentation](https://github.com/wiktor-k/openpgp-proofs#for-service-providers) on what is precisely required is provided by the original creator of decentralized OpenPGP identity proofs.
|