Changes between Version 3 and Version 4 of doc/developer/TokenArchitecture

Show
Ignore:
Timestamp:
05/03/07 18:47:20 (14 years ago)
Author:
benoitg
Comment:

WIP

Legend:

Unmodified
Added
Removed
Modified
  • doc/developer/TokenArchitecture

    v3 v4  
    1717 * is_reusable:  Is the connection reusable? (normally, yes) 
    1818 
    19 tokens 
     19tokens_template_valid_nodes (Unfortunately, for hotels selling 24h access to their clients, we have to consider that their network may consist of more than one node.  If the token has no entry in this table, it's considered valid everywhere on the Network (and it's peers)) 
     20 * token_id 
     21 * token_valid_at_node 
     22 
     23tokens (merge what's left of it back in connections?) 
    2024 * token_id 
    2125 * token_status 
    22  * token_creation_date 
    23  * token_expiration_date: A computed value 
     26 * token_creation_date (not the same as connection start time) 
    2427 * token_issuer:  A user in the system.  User responsable for the creation of the token (not necessarily the same as the one using it)  
    2528 * token_owner:  The user that can USE the token. 
    26  
    27 tokens_valid_nodes (Unfortunately, for hotels selling 24h access to their clients, we have to consider that their network may consist of more than one node.  If the token has no entry in this table, it's considered valid everywhere on the Network (and it's peers)) 
    28  * token_id 
    29  * token_valid_at_node 
    3029 
    3130When a connection is established, the values in the tokens table are used, along with eventual network policies (maximum monthly data transfer, maximum connection time) or node policies (opening hours) to calculate max_data_transfer and expiration_date in the connection table.  This calculation is expensive, but once done, all the auth server has to do is validate max_data_transfer and expiration_date which is practically free.