Ticket #19 (new Feature Request: None)

Opened 3 years ago

Last modified 5 months ago

Per user MAC address whitelisting

Reported by: benoitg Assigned to:
Priority: normal Milestone: WifiDog Auth Server 2.0
Component: Auth server, Authentication, permissions and access control Keywords:
Cc:

Description (Last modified by max-horvath)

If enabled by the network, will allow a device with a specific MAC adress to be considered "logged-in" without a login page, probably under a different bandwidth policy than full token authentication. This may require some changes on the gateway.

Attachments

Change History

10/25/05 10:33:13 changed by max-horvath 

Logged In: YES 
user_id=1359416

This feature has been implemented in the gateway, hasn't it?

So this feature request might be closed ...

10/25/05 13:11:14 changed by benoitg 

Logged In: YES 
user_id=597400

No, the feature implemented in the gateway does not serve the 
same purpose.  This is meant, for example, for someone who 
has a WiFi phone and whant it whitelisted throughout the 
network.

01/23/06 00:11:00 changed by benoitg

  • version deleted.
  • component changed from Auth server: Features to Auth server: Features.
  • description changed.

01/23/06 00:58:13 changed by max-horvath

Well, I like the idea as is ...

The most comfortable way would be if a registered user could enter say 2 or 3 MAC ids in his profile.

If whitelisting would be possible for the network administrator this could result too much work the more nodes and users a network gets ...

The only problem we have is, how to detect, if a user cheats. He could just enter the MAC id of his notebook and voila - he'd never see the login screen again ...

This is kinda though ...

02/22/06 11:41:49 changed by max-horvath

  • status changed from assigned to new.
  • owner deleted.
  • version set to Auth Server SVN.
  • component changed from Auth server: Features to Auth server: Authentication.
  • milestone set to WifiDog Auth Server 2.0.

06/10/06 16:37:17 changed by max-horvath

  • description changed.

01/22/07 15:38:56 changed by benoitg

  • component changed from Auth server: Authentication to Auth server, Authentication.

05/23/08 17:42:12 changed by anonymous

One way around this would be to add device classes. A user for instance wouldn't just add a mac address but "a sip device mac address". Sip devices will only be allowed to use ports used by the sip protocol. And other devices their respective protocol ports.

Add/Change #19 (Per user MAC address whitelisting)