userok: Don't double check for expiry

rxkad_GetServerInfo returns an error if you attempt to get server
information using a connection whose tokens have already expired.

The additional check for expiry in the userOK routines is therefore
not required - they'll never be reached, because GetServerInfo will
already have errored out.

Change-Id: I7b1a97249d40b12a2aae4009971a9b676700870e
Reviewed-on: http://gerrit.openafs.org/2753
Reviewed-by: Derrick Brashear <shadow@dementia.org>
Tested-by: Derrick Brashear <shadow@dementia.org>

diff --git a/src/auth/userok.c b/src/auth/userok.c
index 54d1f0c..28e715a 100644 (file)
--- a/src/auth/userok.c
+++ b/src/auth/userok.c
@@ -466,14 +466,6 @@ rxkadSuperUser(struct afsconf_dir *adir, struct rx_call *acall, char *namep)
     if (code)
        return 0;               /* bogus connection/other error */
 
-    /* don't bother checking anything else if tix have expired */
-#ifdef AFS_PTHREAD_ENV
-    if (exp < clock_Sec())
-#else
-    if (exp < FT_ApproxTime())
-#endif
-       return 0;               /* expired tix */
-
     return kerberosSuperUser(adir, tname, tinst, tcell, namep);
 }