X-Git-Url: http://git.openafs.org/?p=openafs-wiki.git;a=blobdiff_plain;f=WindowsK5AfsServicePrincipal.mdwn;h=e1a710e13ee6113840183191ba1d64b28c23c9ef;hp=95e616ed92053544a53a830b4941ef030d815453;hb=a84928554afc5f39b85c53771aeedf74ef72ad81;hpb=bc411d59e4c4872b9d4a97b3cfe7ccccbfd0c7c6

diff --git a/WindowsK5AfsServicePrincipal.mdwn b/WindowsK5AfsServicePrincipal.mdwn
index 95e616e..e1a710e 100644
--- a/WindowsK5AfsServicePrincipal.mdwn
+++ b/WindowsK5AfsServicePrincipal.mdwn
@@ -166,4 +166,4 @@ If your pts protection server user names in afs and the users names you create i
 
 The reason one would do this is during the transition to K5. Once you have your K5 servers and your [[KeyFile]] configured to contain the old afs kaserver principal and the new K5 service principal you can continue to run the kaserver until your afs clients are configured to use K5 only and wean yourself off the kaserver. The downside of this is having 2 passwords, one in the kaserver and one in the K5 server and not confusing the users.
 
--- [[JohnSopko]] - 24 Jul 2007
+-- John Sopko - 24 Jul 2007