Is there any defintion of the protocol used between the gateway and auth server to verify users and communicate. I see lots of good information in the Intoduction.txt defining classes and sort of a high level abstract of what goes on between the gateway and the auth server, but i don't see message formats, transport mechanisms, state machine things, and what not.

I think there is a place for this as lots of people are trying to write c versions of the gateway to run on embedded hardwares and defining independently of the source code things referred to in it; like the ticket, what punching the ticket means, what http codes are sent back forth and what they mean, etcetera, could be really helpful.

I have started below with some VERY rough beginnings after looking through the gateway src for too many hours.


A transport layer virtual circuit established between two programs for the purpose of communication.;
The basic unit of NOCAT communication, consisting of a HTTP GETs, POSTs, REDIRECTs and status codes.;
The concept describing the nocat state information passed between gateways and clients, clients and auth servers, auth servers and gateways. Tickets can be punched, authenticated, verified, thrown in someone's face, and so much more.;
A program implementing the gateway side of the nocat protocol;
auth server
A program implementing the auth server side of the nocat protocol.;
  • NOCAT Message
    1. Message Types
  • NOCAT messages consist HTTP Gets, POSTs, REDIRECTs, and status codes sent from the gateway to auth server and auth server to gateway.

    Location: https://AuthServiceAddr/cgi-bin/login?token=token_value&timeout=timeout_value&redirect=original_destination_url_of_client&mac=clients_mac_address <html> <body bgcolor="white" text="black"> You should be redirected now. If not, click <a href="">here.</a> </body> </html>}}}


    Hash: SHA1

    Timeout IdleTimeout Token clients_token Mode renew|possibly something else Mac clients_mac User username Action Permit|DENY|possibly something else line=



    6 NOCAT Firewall interactions