11 Commits

Author	SHA1	Message	Date
Ken Moore	2ac91c7c70	Get all the MD5 key generation/matching functional for the server/bridge. Also add an internal 1 minute timer to the bridge connections just to check/remove any broken connections as necessary.	2016-05-23 10:31:49 -04:00
Ken Moore	376a903991	Fix up the bridge/server connection management stuff. Now the server will automatically check/re-connect as needed.	2016-05-23 10:05:09 -04:00
Ken Moore	13fe684d78	Get the final bridge systems setup. Seems to be functioning perfectly now.	2016-05-20 14:46:47 -04:00
Ken Moore	23c254e11e	Get a lot more of the bridge/server connections functional. Just have to work through a mismatch between server/client MD5 sums of valid keys.	2016-05-20 14:11:06 -04:00
Ken Moore	d8a0faea79	Clean up the server and bridge systems so that connections are now successful as needed.	2016-05-20 12:40:32 -04:00
Ken Moore	6e07eb7c49	Commit another batch of fine-tuning for the bridge/server. Still not getting the server->bridge connection for some reason - working on it...	2016-05-18 14:44:42 -04:00
Ken Moore	dc14b0c89b	Fix up all the file paths and such needed for sysadm-bridge to function. Now it should be usable when run either as root or as a user.	2016-05-18 13:40:54 -04:00
Ken Moore	94596117ed	API CHANGE: Get the sysadm-bridge all finished up. Now to add the necessary bits to the server/client so we can try using it. ... NOTE: There is a special API/event for the bridge to announce which server/client connections are available (clients will see only servers, and vice versa) The syntax for this event is: { "namespace":"events", "name":"bridge", "id":"", "args":{ "available_connections":["ID1","ID2", etc..] } } Note that the available_connections are *all* the connections available at that time (it is not a difference from a previous state), so there may be both new ID's in the list and ID's which are no longer listed. This event will get sent out any time a new connection/disconnection is made from the bridge which impacts the current connection (so a client will only get the event when a server connects/disconnects and vice versa).	2016-05-10 10:49:33 -04:00
Ken Moore	45cec48f3c	Setup the authorization manager for the sysadm-bridge. The SSL authentication procedures for Bridge<-->System should now be completely functional.	2016-05-04 14:45:59 -04:00
Ken Moore	26f54ff4f0	Simply the server layout of the bridge	2016-05-02 14:57:49 -04:00
Ken Moore	bd863b70d7	Add the beginning of a new "sysadm-bridge" utility.	2016-05-02 14:34:18 -04:00