Apache Superset #

Requirements #

Apache Superset has built in support for SEP.

SEP Versions 350-e and higher can use the preferred mechanism of a trino connection. It is powered by the SQLAlchemy driver and allows full usage of SQL as supported by Trino, and therefore SEP.

Older versions need to use the legacy support with presto connection. It uses the PyHive driver and therefore does not support all supported SQL syntax.

Connection #

Get the necessary connection information for your cluster:

  • Username
  • Password
  • Host
  • Port

Superset understands the SEP concept of catalogs. You can create a connection with or without a specified catalog:

  • trino://{username}:{password}@{hostname}:{port}/{catalog}
  • trino://{username}:{password}@{hostname}:{port}

Once you have gathered this information, you can create a new connection in Superset:

  • Select Data > Databases, and click the + Database button.
  • Enter the connection string formed from your connection information.
  • Test the connection, if desired.
  • Click Add.


Any SEP cluster that requires authentication is required to use TLS/HTTPS. If the best practice of using a globally trusted certificate is implemented, you can use the HTTPS URL of the cluster in the connection string.

If the certificate is not globally trusted, you need to configure the SEP certificate for TLS/SSL access from Superset on the Superset server.

Authentication #

You can configure the same authentication provider for Superset and SEP. As a result, the same credentials can be used to log in to either system.

Authentication providers supported by both systems include LDAP and OAuth2:

Resources #