Print this page
4213 Missing spaces in man pages


 109 .LP
 110 The following are examples of valid principal names:
 111 
 112 .sp
 113 .in +2
 114 .nf
 115         joe
 116         joe/admin
 117         joe@ENG.ACME.COM
 118         joe/admin@ENG.ACME.COM
 119         rlogin/bigmachine.eng.acme.com@ENG.ACME.COM
 120         host/bigmachine.eng.acme.com@ENG.ACME.COM
 121 .fi
 122 .in -2
 123 .sp
 124 
 125 .sp
 126 .LP
 127 The first four cases are \fIuser principals\fR. In the first two cases, it is
 128 assumed that the user \fBjoe\fR is in the same realm as the client, so no realm
 129 is specified. Note that \fBjoe\fRand \fBjoe/admin\fR are different principals,
 130 even if the same user uses them; \fBjoe/admin\fR has different privileges from
 131 \fBjoe\fR. The fifth case is a \fIservice principal\fR, while the final case is
 132 a \fIhost principal\fR. The word \fBhost\fR is required for host principals.
 133 With host principals, the instance is the fully qualified hostname. Note that
 134 the words \fBadmin\fR and \fBhost\fR are reserved keywords.
 135 
 136 .SH SEE ALSO
 137 .sp
 138 .LP
 139 \fBkdestroy\fR(1), \fBkinit\fR(1), \fBklist\fR(1), \fBkpasswd\fR(1),
 140 \fBkrb5.conf\fR(4), \fBkrb5envvar\fR(5)
 141 .sp
 142 .LP
 143 \fISystem Administration Guide: Security Services\fR
 144 .SH NOTES
 145 .sp
 146 .LP
 147 In previous releases of the Solaris operating system, the Solaris Kerberos
 148 implementation was referred to as the "Sun Enterprise Authentication Mechanism"
 149 (SEAM).


 109 .LP
 110 The following are examples of valid principal names:
 111 
 112 .sp
 113 .in +2
 114 .nf
 115         joe
 116         joe/admin
 117         joe@ENG.ACME.COM
 118         joe/admin@ENG.ACME.COM
 119         rlogin/bigmachine.eng.acme.com@ENG.ACME.COM
 120         host/bigmachine.eng.acme.com@ENG.ACME.COM
 121 .fi
 122 .in -2
 123 .sp
 124 
 125 .sp
 126 .LP
 127 The first four cases are \fIuser principals\fR. In the first two cases, it is
 128 assumed that the user \fBjoe\fR is in the same realm as the client, so no realm
 129 is specified. Note that \fBjoe\fR and \fBjoe/admin\fR are different principals,
 130 even if the same user uses them; \fBjoe/admin\fR has different privileges from
 131 \fBjoe\fR. The fifth case is a \fIservice principal\fR, while the final case is
 132 a \fIhost principal\fR. The word \fBhost\fR is required for host principals.
 133 With host principals, the instance is the fully qualified hostname. Note that
 134 the words \fBadmin\fR and \fBhost\fR are reserved keywords.
 135 
 136 .SH SEE ALSO
 137 .sp
 138 .LP
 139 \fBkdestroy\fR(1), \fBkinit\fR(1), \fBklist\fR(1), \fBkpasswd\fR(1),
 140 \fBkrb5.conf\fR(4), \fBkrb5envvar\fR(5)
 141 .sp
 142 .LP
 143 \fISystem Administration Guide: Security Services\fR
 144 .SH NOTES
 145 .sp
 146 .LP
 147 In previous releases of the Solaris operating system, the Solaris Kerberos
 148 implementation was referred to as the "Sun Enterprise Authentication Mechanism"
 149 (SEAM).