Ticket #289 (new Feature Request)

Opened 2 years ago

Last modified 2 years ago

Support the "Free tokens tied to purchase" model

Reported by: stricjux@email.si Assigned to:
Priority: normal Milestone:
Component: Auth server, Authentication, permissions and access control Keywords: token, authentication, admin interface
Cc:

Description (Last modified by benoitg)

This is the "Free tokens tied to purchase" model, see WirelessCommunityModels. We already have a full software design ready for it. The probable data model is already documented: doc/developer/TokenArchitecture.

None of it involve changes of any kind on the gateway (it already supports all the necessary concepts). We do however need this to be completed to manage permissions for persistent tokens: doc/developer/UserRolesArchitecture

Attachments

Change History

01/22/07 15:30:25 changed by benoitg

  • owner changed.
  • type changed from Bug report to Feature Request.
  • component changed from Gateway and Auth server to Auth server, Authentication.
  • description changed.
  • summary changed from add support for one-time-use tokens to Support the "Free tokens tied to purchase" model.

The original submiter's description follows:

Add support for one-time-use tokens that would enable wifi hotspots to allow users a one-time logon for a limited time. In my view especially applicable to internet cafees - ie. to offer a surf_with_coffee service, where you would need to generate one-day-valid tokens.

Proposed features:

1. a) GATEWAY-INTERFACE: Generate a token (user/pass) with limited lifetime on request via gateway-interface. Admin should be able to generate different token classes (instead of setting the parameters every time). Token classes are defined in AUTH-SERVER. Lifetime starts counting down when user logs in.

1. b) AUTH-SERVER: On per-gateway basis or globally:
Admin: Create token classes.
Admin: Add support for batch generation of tokens (wifidog generates a html/pdf file availible for download from admin page). Would be nice to have an overview of used/active/non_used tokens.

1. c) GATEWAY-INTERFACE:
Globally: Add new user class: Token_master that has the credentials to create tokens, kick tokens off the network, track currently active tokens.

2. GATEWAY-INTERFACE:
Generate a token that tracks user time - when user disconnects from network, a report is generated (used time/bandwidth) and delivered to screen / log. Token_master has the credentials to monitor the reports.

PS: I have no clue on where to start, but I would like to actively help in development of these features. Please contact me.

Add/Change #289 (Support the "Free tokens tied to purchase" model)