Lines Matching full:example
55 @example
67 @end example
89 @example
102 @end example
113 @example
115 @end example
124 @example
126 @end example
134 @example
138 @end example
161 @example
172 @end example
176 @example
186 @end example
190 following example (note that the entries here are truncated for
280 @example
281 kadmin -l check REALM.EXAMPLE.ORG
282 @end example
292 @example
305 @end example
315 @example
317 @end example
344 In the example below @samp{lha/admin} can change every principal in the
351 @example
356 @end example
369 @example
375 @end example
389 @example
394 @end example
413 @example
416 @end example
497 @example
501 @end example
512 @example
514 @end example
516 This was just an hands-on example to make sure that everything was
561 the full name of the principal (for example
574 @example
576 @end example
578 @example
580 @end example
591 @example
594 @end example
676 @example
679 @end example
686 @example
693 @end example
697 @example
703 @end example
707 @example
712 @end example
715 support specifiying that credential to use. The example below will
719 @example
725 @end example
755 @samp{OTHER.REALM}, but not the opposite. In the example above, the
762 @example
790 @end example
827 @example
832 @end example
834 In the following example, the realm @code{STACKEN.KTH.SE} only has
844 @example
852 @end example
886 For example, again consider the @code{[capaths]} entry above for the
906 @subsection Active Directory forest example
916 For example, suppose an organization has a Heimdal realm
917 @code{EXAMPLE.COM}, a Windows Active Directory realm
918 @code{WIN.EXAMPLE.COM}, and then child Active Directory realms
919 @code{ENGR.WIN.EXAMPLE.COM} and @code{SALES.WIN.EXAMPLE.COM}. The
921 services in any of these realms. The @code{EXAMPLE.COM} KDC (and
925 @example
927 ENGR.WIN.EXAMPLE.COM = @{
928 EXAMPLE.COM = WIN.EXAMPLE.COM
930 SALES.WIN.EXAMPLE.COM = @{
931 EXAMPLE.COM = WIN.EXAMPLE.COM
933 EXAMPLE.COM = @{
934 ENGR.WIN.EXAMPLE.COM = WIN.EXAMPLE.COM
935 SALES.WIN.EXAMPLE.COM = WIN.EXAMPLE.COM
937 @end example
939 The first two blocks allow clients in the @code{ENGR.WIN.EXAMPLE.COM}
940 and @code{SALES.WIN.EXAMPLE.COM} realms to authenticate to services in
941 the @code{EXAMPLE.COM} realm. The third block tells the client (or
943 @code{WIN.EXAMPLE.COM} to reach these realms. Both sides of the
975 An example of the configuration for the realm @code{EXAMPLE.COM}:
977 @example
979 $ORIGIN example.com.
980 _kerberos._tcp SRV 10 1 88 kerberos.example.com.
981 _kerberos._udp SRV 10 1 88 kerberos.example.com.
982 _kerberos._tcp SRV 10 1 88 kerberos-1.example.com.
983 _kerberos._udp SRV 10 1 88 kerberos-1.example.com.
984 _kpasswd._udp SRV 10 1 464 kerberos.example.com.
985 _kerberos-adm._tcp SRV 10 1 749 kerberos.example.com.
987 @end example
1000 An example configuration that informs clients that for the realms
1001 it.example.com and srv.example.com, they should use the realm
1002 EXAMPLE.COM:
1004 @example
1006 $ORIGIN example.com.
1007 _kerberos.it TXT "EXAMPLE.COM"
1008 _kerberos.srv TXT "EXAMPLE.COM"
1010 @end example
1048 in @file{lib/hdb/hdb.schema}. Example from slapd.conf:
1050 @example
1052 @end example
1056 local transport. For example:
1058 @example
1060 by dn.exact="uid=heimdal,dc=services,dc=example,dc=com" write
1064 "uid=heimdal,dc=services,dc=example,dc=com"
1066 @end example
1082 @example
1084 @end example
1091 @example
1093 @end example
1105 @example
1108 dbname = ldap:ou=KerberosPrincipals,dc=example,dc=com
1113 @end example
1127 @example
1129 kadmin> init EXAMPLE.COM
1138 lukeh@@EXAMPLE.COM's Password:
1139 Verifying password - lukeh@@EXAMPLE.COM's Password:
1141 @end example
1146 @example
1148 -w secret -b ou=KerberosPrincipals,dc=example,dc=com \
1150 @end example
1156 @example
1162 @end example
1211 @example
1213 get -p lha/admin@@EXAMPLE.ORG service-principal@@EXAMPLE.ORG
1214 lha/admin@@EXAMPLE.ORG's Password:
1215 @end example
1221 @example
1224 service-principal@@EXAMPLE.ORG
1225 @end example
1235 @example
1238 service-principal@@EXAMPLE.ORG \
1240 @end example
1302 @example
1305 @end example
1318 @example
1321 @end example
1326 @example
1331 @end example
1360 @example
1362 @end example
1377 @example
1379 @end example
1390 @example
1392 @end example
1401 @example
1403 @end example
1411 use kinit to get yourself tickets. For example:
1413 @example
1414 $ kinit -C FILE:$HOME/.certs/lha.crt,$HOME/.certs/lha.key lha@@EXAMPLE.ORG
1418 Principal: lha@@EXAMPLE.ORG
1421 Apr 20 02:08:08 Apr 20 12:08:08 krbtgt/EXAMPLE.ORG@@EXAMPLE.ORG
1422 @end example
1426 @example
1427 $ kinit -C PKCS11:/usr/heimdal/lib/hx509.so lha@@EXAMPLE.ORG
1431 Principal: lha@@EXAMPLE.ORG
1434 Mar 26 23:40:10 Mar 27 09:40:10 krbtgt/EXAMPLE.ORG@@EXAMPLE.ORG
1435 @end example
1441 @example
1446 EXAMPLE.COM = @{
1453 @end example
1457 @example
1467 @end example
1473 @example
1476 lha@@EXAMPLE.ORG:C=SE,O=Stockholm universitet,CN=Love,UID=lha
1477 lha@@EXAMPLE.ORG:CN=Love,UID=lha
1478 @end example
1486 First, you need to generate a CA certificate. This example creates a
1492 @example
1500 @end example
1509 @example
1517 @end example
1528 @example
1536 @end example
1545 @example
1547 @end example
1557 @file{openssl.cnf} as described below. To see a complete example of
1563 To use this example you have to use OpenSSL 0.9.8a or later.
1565 @example
1581 @end example
1585 @example
1588 @end example
1617 @example
1623 @end example
1649 @example
1652 @end example