|
The GOOD news today is that | by hadji | 2007-07-25 15:58:59 |
| It's buried in my response yesterday. :-) |
by bwkaz |
2007-07-25 16:33:45 |
In short: Remote access policies can include a Windows-Groups match. If the user trying to log in is a member of the group, then the policy can apply to them (assuming everything else also allows it to apply). If they're not, then the policy isn't valid.
So you set up a group per policy, and assign the users to those groups. :-) |
|
[ Reply ] |
|
Yes, but I do not see a way to | by hadji | 2007-07-25 16:59:29 |
|
If I understand correctly, it works like this: | by merlin | 2007-07-25 17:01:29 |
|
Yep, that's how it works. | by bwkaz | 2007-07-25 17:08:27 |
|
When I said "RADIUS client", I meant the | by merlin | 2007-07-25 17:12:05 |
|
Yeah, but I don't think that's what hadji wanted. | by bwkaz | 2007-07-25 17:15:25 |
|
You could still sort-of make it work. | by merlin | 2007-07-25 17:18:55 |
|
See...we tried that with a wireless group... | by kiwifruit | 2007-07-25 17:26:18 |
|
The part you're missing is that | by hadji | 2007-07-25 17:31:43 |
|
Client-IP-Address. :-) (n/t) | by bwkaz | 2007-07-25 17:34:46 |
|
The client IP address can be associated with | by hadji | 2007-07-25 18:04:29 |
|
Does this article apply at all? | by merlin | 2007-07-25 18:10:29 |
|
Yes! Yes, it does! Thank you. :-) | by hadji | 2007-07-25 18:14:30 |
|
Google FTW ;) I have no clue really what that | by merlin | 2007-07-25 18:19:07 |
|
Well, it shows what I'm obsessed with. ;-) | by bwkaz | 2007-07-25 18:16:26 |
|
In IAS 2k3: | by bwkaz | 2007-07-25 18:12:21 |
|
It's always fun when you change RADIUS | by hadji | 2007-07-25 18:27:07 |
|
\o/ (n/t) | by hadji | 2007-07-25 18:27:38 |
