Skip to main content

How Does It Work?

TRASAGATE is a relatively young project with a rapidly evolving API and workflow. However, we are committed to maintaining up-to-date documentation to ensure your success with TRASAGATE.

If you encounter any issues while using a feature, please reach out to us in our community discussion forum.

Working Concepts​

TRASAGATE manages access for users (including DevOps, software developers, marketing teams, and third-party vendors) to services (such as SSH, RDP, Web, and Database). Access control decisions are based on the access policies and privileges defined by administrators.

Once TRASAGATE is installed and configured, users will access servers and services through the TRASAGATE access proxy.

How Do Users Access Services?​

TRASAGATE currently supports the following connection methods:

  • RDP: Access is available only through the TRASAGATE RDP client (a web application accessible via a browser).
  • SSH: Supported clients include the TRASAGATE SSH client (web application accessible via a browser), *nix terminal SSH client, Putty, Bitvise, MobaXterm, and essentially any SSH client available.
  • HTTP: Users can browse as usual, with sessions managed by the TRASAGATE browser extension.
  • Database (MySQL only): Access is available through the MySQL client you are already using.

Basic Workflow​

  1. Create/Import User Profiles: Set up or import the profiles of users who will need access.
  2. Create/Import Service Profiles: Define or import the services that will be accessed.
  3. Create Access Policies: Establish the rules and conditions under which access is granted.
  4. Assign Users to Services (Access Mapping): Map users or user groups to the relevant services or service groups.
  5. Test Access: Ensure that the access configurations are functioning as expected.
  6. Monitor Access: Continuously oversee access activity to ensure security and compliance.