Force to reauthenticate to webauth after reboot

Unanswered Question
Oct 23rd, 2007
User Badges:
  • Green, 3000 points or more

2100 wireless lan controller

1130 AP's in H-Reap mode

Static WEP and Web Authentication


The problem is when clients, who are connected and authenticated reboot their machines, it is not necessary for them to login to the webauth page again. This brings up a security concern obviously. Is there a way to force the clients to re-authenticate? I was thinking about a small idle timeout but I don't want users to have to login all day long.


Thanks.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3 (2 ratings)
Loading.
dennischolmes Tue, 10/23/2007 - 18:40
User Badges:
  • Gold, 750 points or more

The idle user timeout should be set to something like 6 minutes already. Are you authenticating against the local controller database? I suspect you are. Bounce the authentication off a RADIUS or IAS server.

Scott Pickles Tue, 10/23/2007 - 19:26
User Badges:

What method are you using to validate credentials in the web authentication? Local database, RADIUS, LDAP, etc.? Unfortunately, without clicking "logout" the session remains active. At this point, my only thoughts are to use something like AD (RADIUS/IAS) or the Lobby function where you can specify when a particular account times out.


Regards,

Scott

acomiskey Wed, 10/24/2007 - 05:23
User Badges:
  • Green, 3000 points or more

Thanks guys, I am using a RADIUS server for authentication. I do think the idle timeout is the default 300 seconds. But it doesn't take that long to reboot a pc.

acomiskey Thu, 10/25/2007 - 05:36
User Badges:
  • Green, 3000 points or more

Anyone have any other ideas?


So the only way to be logged out from the webauth is to physically press the logout button or for the idle timer to expire?

acomiskey Fri, 10/26/2007 - 06:33
User Badges:
  • Green, 3000 points or more

Why wouldn't they be disassociated/unauthenticated when the pc reboots?

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode