Hi,
Is this is a known issue with Radiator 3.16? Does anyone have Radiator
3.16 successfully authenticating against an AD2008 domain? [I realize
that 3.16 is a little dated ... ]
3.16 is hideously outdatedand came out years before AD2008 was even a
twinkle
int he eye of MS - I wouldnt
Hugh,
Thanks for your response.
I have tried LSA with following config and it did not work.
AuthBy LSA
Identifier LSA
Domain xxx.xxx.xxx
Group networking_staff
UsernameMatchesWithoutRealm
EAPType MSCHAP-V2
/AuthBy
On 11/09/2011 05:37 PM, Kim, Steve wrote:
Hello Steve,
I have tried LSA with following config and it did not work.
AuthBy LSA
Identifier LSA
Domain xxx.xxx.xxx
The Domain here is a valid Windows domain?
Group networking_staff
Hi Heikki,
Yes, I have checked the privileges.
So, this time, I ran the radiator from the services.msc which starts with local
system account instead of command line.
It looked like it is working in a way, but I got following error:
Wed Nov 9 10:49:10 2011: DEBUG: Handling with
On 11/08/2011 08:36 PM, Rafael Rodriguez wrote:
Hello Rafael,
Here is what we need:
Juniper (JUNOS) devices to authenticate users via TACACS+.
Authentication of the users should be done via 1) LDAPS queries to
Active Directory and/or 2) local accounts. If Authentication is done by
1) then
On 11/09/2011 05:58 PM, Kim, Steve wrote:
Hello Steve,
Yes, I have checked the privileges.
So, this time, I ran the radiator from the services.msc which starts with
local system account instead of command line.
It looked like it is working in a way, but I got following error:
Yes, it's
It's sweet! It is working.
Thanks for your help.
My initial setup is working with your help.
However, I'd like to configure following with a Cisco router and AD via TACACS+
Here is the Cisco configuration:
aaa authorization commands 0 default group tacacs+ if-authenticated
aaa authorization
Yup, we're seriously dragging, in terms of versions
I twinked with the Handler; turns out the version below works fine with
this new AD2008 domain:
Handler Client-Identifier=vdops-mgmt
AuthBy GROUP
AuthByPolicy ContinueUntilAccept
For AuthBy SQL, does anyone know if sql returned values from AuthSelect and
configured as 'request' with AuthColumnDef are suppose to be added to the
request packet if the authentication fails? It does add if success, but
doesn't seem to add values to the request packet if it fails. I don't
