summaryrefslogtreecommitdiff
path: root/doc/handbook
diff options
context:
space:
mode:
authorng0 <ng0@n0.is>2019-03-05 20:12:06 +0000
committerng0 <ng0@n0.is>2019-03-05 20:12:06 +0000
commita61d901d0e331e4cd180303a02016dff0c4cdf56 (patch)
tree9e22cd5b1268b48dbbe67f3513c1e6092d115192 /doc/handbook
parent4e4039ea6d8341b5c7e4e7a34b44d024d8a21d51 (diff)
texinfo: format
Diffstat (limited to 'doc/handbook')
-rw-r--r--doc/handbook/chapters/user.texi12
1 files changed, 8 insertions, 4 deletions
diff --git a/doc/handbook/chapters/user.texi b/doc/handbook/chapters/user.texi
index 1300b2bb6..e7ab51335 100644
--- a/doc/handbook/chapters/user.texi
+++ b/doc/handbook/chapters/user.texi
@@ -1982,10 +1982,14 @@ and enable the service, so that your zone is migrated automatically.
@section reclaimID Identity Provider
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, 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.
+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, 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::