Lines Matching full:cross
27 * Cross realm::
660 @node Credential cache server - KCM, Cross realm, Encryption types and salting, Setting up a realm
729 @node Cross realm, Transit policy, Credential cache server - KCM, Setting up a realm
730 @section Cross realm
731 @cindex Cross realm
792 @node Transit policy, Setting up DNS, Cross realm, Setting up a realm
797 cross-realm trust with every realm to which you wish to authenticate
799 multi-hop cross-realm trust where a client principal in realm A
801 both A and C have cross-realm trust relationships. In this situation,
802 A and C need not set up cross-realm principals between each other.
804 If you want to use cross-realm authentication through an intermediate
814 @subsection Allowing cross-realm transits
830 SERVER-REALM = PERMITTED-CROSS-REALMS ...
835 direct cross-realm set up with @code{KTH.SE}. @code{KTH.SE} has
836 direct cross-realm set up with @code{STACKEN.KTH.SE} and @code{SU.SE}.
837 @code{DSV.SU.SE} only has direct cross-realm set up with @code{SU.SE}.
854 The first entry allows cross-realm authentication from clients in
856 @code{STACKEN.KTH.SE}. The second entry allows cross-realm
867 The order of the @code{PERMITTED-CROSS-REALMS} is not important when
868 doing transit cross realm verification.
870 @subsection Configuring client cross-realm transits
874 their local realm does not have cross-realm trust. This can be done
878 a referral to the client when the client requests a cross-realm ticket
882 For client configuration, the order of @code{PERMITTED-CROSS-REALMS}
891 cross-realm to the @code{KTH.SE} realm (the first realm listed in the
892 @code{PERMITTED-CROSS-REALMS} section), and then from there to
896 the first realm in @code{PERMITTED-CROSS-REALMS} is used. If, for
912 on organizational unit). One generally establishes cross-realm trust
944 configuration are needed for bi-directional transited cross-realm
947 @c To test the cross realm configuration, use:
997 same cross realm trust and made to believe they are talking to the