Alan DeKok wrote:
Craig Huckabee <[EMAIL PROTECTED]> wrote:
Doesn't work - both %{Foo} and %{request:Foo} come back empty when
setting Foo on the check line in users.
Hmm...
Anything else you can think of ?
Try using another attribute.
Or, follow the code execution in src/modules/
Craig Huckabee <[EMAIL PROTECTED]> wrote:
> Doesn't work - both %{Foo} and %{request:Foo} come back empty when
> setting Foo on the check line in users.
Hmm...
> Anything else you can think of ?
Try using another attribute.
Or, follow the code execution in src/modules/rlm_files/rlm_files
Alan DeKok wrote:
Craig Huckabee <[EMAIL PROTECTED]> wrote:
However, if I use this:
DEFAULT User-Name =~ "^([^/]+)/(.*)"
Foo = `%{2}`
...
then attempt to look at Foo using %{reply:Foo}, I get the expected value
and the filter works.
Try the original, but look for foo in %{Foo}, or %{r
Craig Huckabee <[EMAIL PROTECTED]> wrote:
> However, if I use this:
>
> DEFAULT User-Name =~ "^([^/]+)/(.*)"
> Foo = `%{2}`
> ...
>
> then attempt to look at Foo using %{reply:Foo}, I get the expected value
> and the filter works.
Try the original, but look for foo in %{Foo}, or %{reques
Craig Huckabee wrote:
attr_rewrite works but breaks EAP for me :(
I've reattempted using the users file again, and double checked that
files does indeed come before the ldap sections in the authorize
section - still get a blank filter.
A debug run shows that files is indeed getting processed
Craig Huckabee <[EMAIL PROTECTED]> wrote:
>Trying to follow the examples given in variables.txt and using the
> 'users' file, things like:
>
> DEFAULT User-Name =~ "^([^/]+)/(.*)",
> Everything = `%{0}`,
> Test-Variable = `%{2}`,
> Fall-Through = yes
>
> causes a core du
Another data point -
Trying to follow the examples given in variables.txt and using the
'users' file, things like:
DEFAULT User-Name =~ "^([^/]+)/(.*)",
Everything = `%{0}`,
Test-Variable = `%{2}`,
Fall-Through = yes
causes a core dump on startup.
--Craig
-
List info
Kostas Kalevras wrote:
The other idea is to use attr_rewrite as already suggested. In any case, make
sure that the files module comes before ldap in the authorize section for the
above to work.
attr_rewrite works but breaks EAP for me :(
I've reattempted using the users file again, and double c
On Wed, 5 May 2004, Craig Huckabee wrote:
>
>
> Kostas Kalevras wrote:
>
> >
> > The above won't work. You can't just add the User-Name line in the rlm_ldap
> > configuration and expect it to work.
>
> I didn't expect it to just work, but I wanted to at least try something
> before posting a quest
Kostas Kalevras wrote:
The above won't work. You can't just add the User-Name line in the rlm_ldap
configuration and expect it to work.
I didn't expect it to just work, but I wanted to at least try something
before posting a question. The documentation isn't as clear as your
answer so I was g
On Tue, 4 May 2004, Craig Huckabee wrote:
>
> Where can the regular expressions discussed in 'doc/variables.txt' be
> used ? I'd like to modify the User-Name attribute as passed in for use
> as a filter for rlm_ldap.
>
> For example, during an EAP-TLS, I get an EAP packet like this:
>
> NAS-IP-Ad
Where can the regular expressions discussed in 'doc/variables.txt' be
used ? I'd like to modify the User-Name attribute as passed in for use
as a filter for rlm_ldap.
For example, during an EAP-TLS, I get an EAP packet like this:
NAS-IP-Address = ...
NAS-Port-Type = Async
User-Name = "host/g21
12 matches
Mail list logo
