summaryrefslogtreecommitdiff
path: root/doc/handbook/chapters/user.texi
diff options
context:
space:
mode:
Diffstat (limited to 'doc/handbook/chapters/user.texi')
-rw-r--r--doc/handbook/chapters/user.texi10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/handbook/chapters/user.texi b/doc/handbook/chapters/user.texi
index 12d9fc797..3f99be7a8 100644
--- a/doc/handbook/chapters/user.texi
+++ b/doc/handbook/chapters/user.texi
@@ -26,7 +26,7 @@ always welcome.
* First steps - Using the GNUnet VPN::
* File-sharing::
* The GNU Name System::
-* re@@claim Identity Provider::
+* reclaimID Identity Provider::
* Using the Virtual Public Network::
@end menu
@@ -1978,14 +1978,14 @@ seamlessly.
At this point you might want to write for example a systemd unit file to start
and enable the service, so that your zone is migrated automatically.
-@node re@@claim Identity Provider
-@section re@@claim Identity Provider
+@node reclaimID Identity Provider
+@section reclaimID Identity Provider
-The re:claim Identity Provider (IdP) is a decentralized IdP service.
+The reclaimID Identity Provider (IdP) is a decentralized IdP service.
It allows its users to manage and authorize third parties to access their identity attributes such as email or shipping addresses.
It basically mimics the concepts of centralized IdPs, such as those offered by Google or Facebook.
-Like other IdPs, re:claim features an (optional) OpenID-Connect 1.0-compliant protocol layer that can be used for websites to integrate re:claim as an Identity Provider with little effort.
+Like other IdPs, reclaimID features an (optional) OpenID-Connect 1.0-compliant protocol layer that can be used for websites to integrate reclaimID as an Identity Provider with little effort.
@menu
* Managing Attributes::