[OpenAFS] 1.3.82 in AIX 5.2.0.5

[Tomasz Skarupa]

Hello all,

I compiled the 1.3.82 client on AIX 5.2.0.5, single processor,
32-Bit kernel, VAC 6, anything else is GNU software (flex, bison,
etc...).

everything works fine, except getting PAG tokens from kaserver...
in the same cell, from same servers, but from IBM AFS clients, I get
PAG tokens...

I can't understand why the "(PAG/UID Based Tokens)" section is
missing in the "tokens" command output:


###############

Tokens held by the Cache Manager:

User's (AFS ID XXX) tokens for afs@domain.tld [Expires May  5 20:18]
   --End of list--

###############


is that a compilation error on my side (i'm everything but a guru...
^_^) or the 1.3.82 code isn't "ready" for AIX 5.2's PAG system?

i've used curpag binary for aix 5.2 from IBM AFS 3.6-11, and the
output is:


###############

0

###############


here after I paste an extract from IBM AFS 3.6-11 readme, where they
talk about the curpag binary I used in my self-compiled set:

> # Curpag binary
> 
> 
> The curpag binary is a small program that prints the pags for the current user session.
> 
> On AIX, when the user authenticates through kerberos, the KRBTKFILE environment variable is not set. If this environment variable is not set, the kerberos tokens are not displayed with the tokens.krb command.
> 
> The value of KRBTKFILE variable is of the following format: /tmp/tktp$PAG where $PAG are the pags associated with the current session. The curpag binary prints $PAG. To set the KRBTKFILE environment variable, issue the following command: $ setenv KRBTKFILE /tmp/tktp`/usr/vice/etc/curpag`.
> 
> The "curpag" binary is distributed with AFS on AIX 4.3 and 5.1 distributions and is in the /usr/vice/etc directory.
> 
> (Noted at Patch 4) 

...and also about:

> # Tokens command and identification of PAG based tokens on AIX 5.x
> 
> 
> Due to a change in the internal implementation of PAG based tokens in AIX 5.x, the command "id --G" can no longer be used to identify PAG based tokens. Therefore, the "tokens" command has been modified to additionally display the "type" of token being displayed, that is to say, PAG based token or UID based token.
> 
> For UID based tokens, the output of the tokens command looks like:
> 
> # tokens
> Tokens held by the Cache Manager (UID Based Tokens) :
> User's (AFS ID 1024) tokens for afs@jupiter.in.ibm.com
> [Expires Apr 11 10:43]
> --End of list--
> 
> For PAG based tokens, the output of the tokens command looks like:
> 
> # tokens
> Tokens held by the Cache Manager (PAG Based Tokens) :
> User's (AFS ID 1024) tokens for afs@jupiter.in.ibm.com
> [Expires Apr 11 10:43]
> --End of list--
> 
> (Noted at Patch 3)

i don't know what's that "change in the internal implementation of
PAG based tokens", but I would like to know if it's my fault or it's
symply not possible yet to get PAG instead of UID-based tokens.

thanks all for your great work, and thanks in advance for any answer!

--
Tom.