Version 2 (modified by Pascal Leclerc, 15 years ago) |
---|
Wifidog Flow Diagram
General Flow Description:
- The client does his initial request, as if he was already connected, (e.g.: http://www.google.ca)
- The Gateway's firewall rules mangle the request to redirect it to a local port on the Gateway. When that's the done, the Gateway provides an HTTP Redirect reply that contains the Gateway ID, Gateway FQDN and other informations
- The Client does his request to the Auth Server as specified by the Gateway
- The Gateway replies with a (potentially custom) splash (login) page
- The Client provides his identification informations (username and password)
- Upon succesful authentication, the client gets an HTTP Redirect to the Gateway's own web server with his authentication proof (a one-time token)
- The Client then connects to the Gateway and thus gives it his token
- The Gateway requests validation of the token from the Auth Server
- The Auth Server confirms the token
- The Gateway then sends a redirect to the Client to obtain the Success Page from the Auth Server
- The Auth Server notifies the Client that his request was successful
Attachments
-
AuthenticationFlow.pdf
(36.4 KB) - added by Robin Jones 14 years ago.
Graphical flow diagram of auth process
-
Wifidog Client Authentication Diagram.pdf
(52.5 KB) - added by ggrike@… 14 years ago.
Cleaned up Robins' Original Flow Diagram
-
FlowDiagram.png
(125.2 KB) - added by benoitg 5 years ago.