Jacob Dawson wrote:
Further testing suggests that neither of the Perl or Realm modules is
applying the Stripped-User-Name in the right scope.
I have no idea what that means. The Stripped-User-Name isn't magic.
It's just an attribute. If it exists in the request list, you can refer
to it
On 15 Jul 2011, at 02:51, Alan DeKok wrote:
Jacob Dawson wrote:
Further testing suggests that neither of the Perl or Realm modules is
applying the Stripped-User-Name in the right scope.
I have no idea what that means. The Stripped-User-Name isn't magic.
It's just an attribute. If it
Jacob Dawson daw...@vt.edu wrote:
Unfortunately, when you set nostrip in the config, it doesn't add a
Stripped-User-Name attribute to the request, but when you unset it,
rlm_realms adds a Stripped-User-Name attribute and also updates the
User-Name attribute to the same value.
I am 90% sure
Phil Mayers p.may...@imperial.ac.uk wrote:
Unfortunately, when you set nostrip in the config, it doesn't add a
Stripped-User-Name attribute to the request, but when you unset it,
rlm_realms adds a Stripped-User-Name attribute and also updates the
User-Name attribute to the same value.
I am
So I played with my copy of the code to change what nostrip being unset means
(now, it writes the Stripped-User-Name attribute, but no longer rewrites the
User-Name attribute with the stripped username), and I'm still running into
problems:
(0) HOKIES : Looking up realm hokies for User-Name =
Further testing suggests that neither of the Perl or Realm modules is applying
the Stripped-User-Name in the right scope. Perl does that first thing, when a
request comes in, and my output says that as soon as perl is done, it's unset.
Similarly, as soon as the hokies realm module is done
6 matches
Mail list logo
