On Sat, Mar 10, 2012 at 5:29 AM, u...@3.am wrote:
So to save lots of time and configuration problem: does your LDAP
store user passwords in clear text or any common hash (e.g. md5,
unix)? If yes, AND you know what the LDAP attribute is, you don't even
need an LDAP section in authenticate.
On 12/03/12 15:44, u...@3.am wrote:
DEFAULT Group == FOO, Pool-Name :=FOO_pool
Group is probably empty. I can't remember what module, if any, fills
it out.
What do you *think* Group will contain? It won't contain LDAP groups.
-
List info/subscribe/unsubscribe? See
On 12/03/12 15:44, u...@3.am wrote:
DEFAULT Group == FOO, Pool-Name :=FOO_pool
Group is probably empty. I can't remember what module, if any, fills
it out.
What do you *think* Group will contain? It won't contain LDAP groups.
I was about to post about this..I just did a test with
Hi,
DEFAULT Group == FOO, Pool-Name :=FOO_pool
Group is probably empty. I can't remember what module, if any, fills
it out.
# The Group and Group-Name attributes are automatically created by
# the Unix module, and do checking against /etc/group automatically.
# This means that
Hi,
DEFAULT Group == FOO, Pool-Name :=FOO_pool
Group is probably empty. I can't remember what module, if any, fills
it out.
# The Group and Group-Name attributes are automatically created by
# the Unix module, and do checking against /etc/group automatically.
# This means
On 12/03/12 18:23, u...@3.am wrote:
...and you just hit on something that solved the problem. It seems that FR was
getting the group info from LDAP indirectly, through the PAM module, which was
Actually, probably not.
It probably gets the groups via nss_ldap, through nssswitch.
-
List
On Sat, Mar 10, 2012 at 10:47 AM, u...@3.am wrote:
Both hashes are supported, thanks for the link. I assume I need to define
something to map to, as well? Like this:
raddb/dictionary: ATTRIBUTE userPassword 3004 string
err... no.
raddb/ldap.attrmap: checkItem
-AppleTalk-Zone
rlm_ldap: LDAP radiusPortLimit mapped to RADIUS Port-Limit
rlm_ldap: LDAP radiusLoginLATPort mapped to RADIUS Login-LAT-Port
rlm_ldap: LDAP radiusReplyMessage mapped to RADIUS Reply-Message
conns: 0x958f390
/usr/etc/raddb/sites-enabled/default[241]: Unknown Auth-Type LDAP
u...@3.am wrote:
Trying to set up a new RADIUS 2.1.12 server with LDAP. It configured and
built
all the modules I need, including rlm_ldap, once I installed the
dependencies. I
took all of the same config files that I have working on servers running
2.1.9 and
2.1.10, but 2.1.12
u...@3.am wrote:
Trying to set up a new RADIUS 2.1.12 server with LDAP. It configured and
built
all the modules I need, including rlm_ldap, once I installed the
dependencies.
I
took all of the same config files that I have working on servers running
2.1.9
and
2.1.10, but 2.1.12
u...@3.am wrote:
Trying to set up a new RADIUS 2.1.12 server with LDAP. It configured and
built
all the modules I need, including rlm_ldap, once I installed the
dependencies.
I
took all of the same config files that I have working on servers running
2.1.9
and
2.1.10, but 2.1.12
On Fri, Mar 09, 2012 at 10:59:46AM -0500, u...@3.am wrote:
authorize {
preprocess
redundant LDAP{
ldap1
ldap2
}
# The ldap module will set Auth-Type to LDAP if it has not
# already
On Sat, Mar 10, 2012 at 3:23 AM, Phil Mayers p.may...@imperial.ac.uk wrote:
On Fri, Mar 09, 2012 at 10:59:46AM -0500, u...@3.am wrote:
authenticate {
#Auth-Type LDAP {
redundant LDAP{
ldap1
ldap2
}
Using ldap in the authenticate
On Sat, Mar 10, 2012 at 3:23 AM, Phil Mayers p.may...@imperial.ac.uk wrote:
On Fri, Mar 09, 2012 at 10:59:46AM -0500, u...@3.am wrote:
authenticate {
#Auth-Type LDAP {
redundant LDAP{
ldap1
ldap2
}
Using ldap in the authenticate
On Sat, Mar 10, 2012 at 5:29 AM, u...@3.am wrote:
So to save lots of time and configuration problem: does your LDAP
store user passwords in clear text or any common hash (e.g. md5,
unix)? If yes, AND you know what the LDAP attribute is, you don't even
need an LDAP section in authenticate.
On Sat, Mar 10, 2012 at 5:29 AM, u...@3.am wrote:
So to save lots of time and configuration problem: does your LDAP
store user passwords in clear text or any common hash (e.g. md5,
unix)? If yes, AND you know what the LDAP attribute is, you don't even
need an LDAP section in authenticate.
On Sat, Mar 10, 2012 at 10:47 AM, u...@3.am wrote:
Both hashes are supported, thanks for the link. I assume I need to define
something to map to, as well? Like this:
raddb/dictionary: ATTRIBUTE userPassword 3004 string
err... no.
raddb/ldap.attrmap: checkItem
17 matches
Mail list logo
