Hi Andreas,
The "username" in the login request is there simply for tracking purposes.
It is not used, nor should it ever be used, for anything but to display a
unique identification in the logs. Even if the username is truncated to 8
bytes you still get a unique identification due to other identifiers that
are added to it.
If you truly need a non-secure full username enable unix security. It will
send the full username (256 character limit) and then extract it out of
the SecEntity structure.
Andy
On Fri, 4 Oct 2013, Andreas-Joachim Peters wrote:
> Could the username length be changed to 32 bytes? We just hit this problem
> at FNAL ...
>
> Cheers Andreas.
>
>
> struct ClientLoginRequest {
> kXR_char streamid[2];
> kXR_unt16 requestid;
> kXR_int32 pid;
> kXR_char username[8];
> kXR_char reserved[2];
> kXR_char capver[1];
> kXR_char role[1];
> kXR_int32 dlen;
> };
>
> ########################################################################
> Use REPLY-ALL to reply to list
>
> To unsubscribe from the XROOTD-DEV list, click the following link:
> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
>
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
