Differences Between SwaggerHub On-Premise 1.x and 2.x

This page summarizes the configuration changes between SwaggerHub On-Premise versions 1.x and 2.x. It is intended for administrators who are planning to migrate from v. 1.x to 2.x or have already done so.


The following features of SwaggerHub On-Premise 1.x are currently not supported in version 2.x, but will be added in future releases:

  • Test LDAP

  • Reports: List of all APIs in the system

Configuration changes

  • The built-in Admin Center (http(s)://SERVER/ui) was replaced with the Admin Console provided by Replicated KOTS. The new Admin Console has similar functionality, but with a few key differences:

  • Updates are now managed by Replicated KOTS.

    • In Internet-connected installations, you can check for updates and install updates directly from the KOTS Admin Console. You can also enable automatic update checks to see new release notifications in the Admin Console.

    • To update an airgapped (offline) installation, you need to download the new airgap bundle from your SwaggerHub Download Portal and then upload it to the Admin Console.

    • You can also install updates from the command line by using the kubectl kots upstream upgrade command.

  • System logs (diagnostic data) are included in support bundles.

  • Maintenance scripts were replaced with the swaggerhub-operator commands.

  • Some configuration options and administrator features were replaced with the swaggerhub-operator commands:

    1.x feature


    Default organization name option


    Test Proxy button


    Sent Test Email button


    Admin Center: License page and users list




    User Management API

Removed features

The following configuration settings were removed in SwaggerHub On-Premise 2.x because these things can be configured at the cluster level or operating system level:

  • SSH users

  • NTP settings

See Also

Publication date: