aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorSchanzenbach, Martin <martin.schanzenbach@aisec.fraunhofer.de>2018-07-07 11:58:06 +0200
committerSchanzenbach, Martin <martin.schanzenbach@aisec.fraunhofer.de>2018-07-07 11:58:06 +0200
commit54ba272c812dfe9b5056bb916379569f41baf24e (patch)
treeb8e12da04b72ca1fe60f8c52f079407d5b40f370 /doc
parentead5b511755860cefc793257120338a44a08c9dd (diff)
downloadgnunet-54ba272c812dfe9b5056bb916379569f41baf24e.tar.gz
gnunet-54ba272c812dfe9b5056bb916379569f41baf24e.zip
fix titles
Diffstat (limited to 'doc')
-rw-r--r--doc/documentation/chapters/user.texi22
1 files changed, 11 insertions, 11 deletions
diff --git a/doc/documentation/chapters/user.texi b/doc/documentation/chapters/user.texi
index 0a62c5fdb..711d1d4a8 100644
--- a/doc/documentation/chapters/user.texi
+++ b/doc/documentation/chapters/user.texi
@@ -26,7 +26,7 @@ always welcome.
26* First steps - Using the GNUnet VPN:: 26* First steps - Using the GNUnet VPN::
27* File-sharing:: 27* File-sharing::
28* The GNU Name System:: 28* The GNU Name System::
29* reclaim:: 29* re@:claim Identity Provider::
30* Using the Virtual Public Network:: 30* Using the Virtual Public Network::
31@end menu 31@end menu
32 32
@@ -1791,8 +1791,8 @@ is thus advisable to disable the namecache by setting the
1791option ``DISABLE'' to ``YES'' in section ``[namecache]''. 1791option ``DISABLE'' to ``YES'' in section ``[namecache]''.
1792 1792
1793 1793
1794@node reclaim 1794@node re@:claim Identity Provider
1795@section re:claim Identity Provider 1795@section re@:claim Identity Provider
1796 1796
1797The re:claim Identity Provider (IdP) is a decentralized IdP service. 1797The re:claim Identity Provider (IdP) is a decentralized IdP service.
1798It allows its users to manage and authorize third parties to access their identity attributes such as email or shipping addresses. 1798It allows its users to manage and authorize third parties to access their identity attributes such as email or shipping addresses.
@@ -1801,13 +1801,13 @@ It basically mimics the concepts of centralized IdPs, such as those offered by G
1801Like 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. 1801Like 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.
1802 1802
1803@menu 1803@menu
1804* reclaim-Attributes:: 1804* Managing Attributes::
1805* reclaim-Authorization:: 1805* Sharing Attributes with Third Parties::
1806* reclaim-Revocation:: 1806* Revoking Authorizations of Third Parties::
1807* reclaim-OpenID:: 1807* Using the OpenID-Connect IdP::
1808@end menu 1808@end menu
1809 1809
1810@node reclaim-Attributes 1810@node Managing Attributes
1811@subsection Managing Attributes 1811@subsection Managing Attributes
1812 1812
1813Before adding attributes to an identity, you must first create an ego: 1813Before adding attributes to an identity, you must first create an ego:
@@ -1834,7 +1834,7 @@ $ gnunet-idp -e "username" -D
1834Currently, and by default, attribute values are interpreted as plain text. 1834Currently, and by default, attribute values are interpreted as plain text.
1835In the future there might be more value types such as X.509 certificate credentials. 1835In the future there might be more value types such as X.509 certificate credentials.
1836 1836
1837@node reclaim-Authorization 1837@node Sharing Attributes with Third Parties
1838@subsection Sharing Attributes with Third Parties 1838@subsection Sharing Attributes with Third Parties
1839 1839
1840If you want to allow a third party such as a website or friend to access to your attributes (or a subset thereof) execute: 1840If you want to allow a third party such as a website or friend to access to your attributes (or a subset thereof) execute:
@@ -1864,7 +1864,7 @@ $ gnunet-idp -e "friend" -T (TODO there is only a REST API for this ATM)
1864@end example 1864@end example
1865 1865
1866 1866
1867@node reclaim-Revocation 1867@node Revoking Authorizations of Third Parties
1868@subsection Revoking Authorizations of Third Parties 1868@subsection Revoking Authorizations of Third Parties
1869 1869
1870If you want to revoke the access of a third party to your attributes you can execute: 1870If you want to revoke the access of a third party to your attributes you can execute:
@@ -1878,7 +1878,7 @@ Please note that if the third party has previously accessed the attribute, there
1878As such, only access to updated data in the future can be revoked. 1878As such, only access to updated data in the future can be revoked.
1879This behaviour is _exactly the same_ as with other IdPs. 1879This behaviour is _exactly the same_ as with other IdPs.
1880 1880
1881@node reclaim-OpenID 1881@node Using the OpenID-Connect IdP
1882@subsection Using the OpenID-Connect IdP 1882@subsection Using the OpenID-Connect IdP
1883 1883
1884TODO: Document setup and REST endpoints 1884TODO: Document setup and REST endpoints