GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.
Admin message
Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.
1. The application (henceforth called *hub app*) should reside on a stand-alone machine, **not** on any of the managed routers.
1. A user will connect to the hub app's URL (after authenticating) and be presented with a list of routers that are available for management. This list may be user specific. Authentication can be done via the same client certificate as in the next step or by other means.
1. Communication with the selected router will be accomplished as a client-side application – all data will be exchanged between the router and client's browser. The router must separately perform certificate-based authentication. This way, no potentially sensitive data will go through the hub app.