introduced username validation. The method
also tries to parse anything in the username
following a "." into an integer. This
requirement is too strict.
Modification:
Remove that requirement.
We also eliminate searching for the pid
on the user URN given to the TPC
client and generate instead a
random 5-digit integer, since
this login 'pid' value is used
only for monitoring purposes.
Result:
Usernames like 'foo.1234:56' are
no longer rejected.
Motivation:
https://rb.dcache.org/r/12234 master@4df20da279b6f8777c3c2ef10619cb44f98cbcc0
introduced username validation. The method also tries to parse anything in the username following a "." into an integer. This requirement is too strict.
Modification:
Remove that requirement. We also eliminate searching for the pid on the user URN given to the TPC client and generate instead a random 5-digit integer, since this login 'pid' value is used only for monitoring purposes.
Result:
Usernames like 'foo.1234:56' are no longer rejected.
Target: master Request: 4.0 Request: 3.5 Request: 3.4 Acked-by: Dmitry Bug: https://rt.dcache.org/Ticket/Display.html?id=9955