2.0.4

• support SpEL (Spring expression language) in the application.yml configuration file; this allows a.o. to mount user-specific volumes for Shiny apps
• ship MonetDB client jar again for usage statistics monitoring with MonetDB
• fix leftover pixels below app iframe
• fix proxy access error when using 2 sessions and OIDC
• fix blank page or 404 when re-accessing a starting proxy
• fix generation of the ShinyProxy RPM package
• document settings for large file uploads in Shiny apps

2.0.3

• a new environment variable SHINYPROXY_OIDC_ACCESS_TOKEN is made available to the Shiny app containers when using the OpenId Connect (OIDC) authentication/authorization back-end; this allows to use the OIDC access token to authenticate against APIs from within the Shiny apps
• fix 'Not authorized to access this proxy' issue which occurred when an admin accessed an app that was already running for another user or when the same user accesses the same app from two different browser sessions

2.0.2

• new setting proxy.bind-address to specify the bind address (hostname or IP address)
• examples on containerized ShinyProxy with Docker Swarm back-end
• no more redirect after logout with Keycloak-backed authentication
• updated documentation on specification of context paths
• support trailing slashes for app URLs
• bug fix: OIDC now respects the context path
• fix authentication: none
• a default configuration file ships with ShinyProxy again

2.0.1

• the display-name is now used as browser tab name, so different Shiny apps in the browser can be more easily discriminated
• support for setting SSL/HTTPS modes in the Keycloak back-end for single sign-on (proxy.keycloak.ssl-required)
• better documentation of the privileged setting in proxy.docker, proxy.kubernetes and for individual app containers
• bug fix: some settings were still using the old (1.x.y) shiny.proxy namespace instead of proxy
• fix support of authentication: none
• fix resolution of proxy.kubernetes.image-pull-* settings for pulling Shiny app container images

2.0.0

• support to manage Shiny apps over an API (launch, shut down) for embedding Shiny apps in larger applications and websites
• new heartbeat mechanism that no longer requires the use of iframes
• support of OpenId Connect authentication
• new YAML configuration to prepare for more advanced features; note that the configuration
  is slightly different from the 1.x.y versions
• better container log names with the image name and time stamp

1.1.1

• support for theming and customization of the ShinyProxy landing page
• stricter adherence to YAML for the ShinyProxy configuration in the application.yml file
• remove 1-pixel border around Shiny app display for certain browsers
• bug fix to make sure a query string e.g. the ?x=y from /app/myApp?x=y is passed properly to the app
• bug fix for kubernetes backend deleting all services

1.1.0

• support to run ShinyProxy inside a container
• support of a Kubernetes back-end
• new property shiny.proxy.container-backend to configure container back-end
• support of setting a custom port per app (using a new port property); this notably allows to run Dash apps inside ShinyProxy (which have 8050 as default port)
• allow for multiple sessions per user/app combination
• new property privileged which, if true allows to run the app containers in a privileged mode
• search LDAP subtree instead of one level
• improved documentation of LDAP configuration
• Keycloak authentication will now fail if username is empty
• removed obsolete navbar dropdown in mobile mode
• added travis support to the repository

1.0.2

• new property shiny.docker.proxy.port-range-max allows to limit the number of ports to be used
  by a single ShinyProxy instance e.g. to allow multiple instances to launch docker containers on a shared Docker Swarm cluster or to limit the number of concurrent apps on a single
  instance
• app-specific environment variables can be specified in the docker-env property inside the app configuration, similarly to docker-env-file
• the logo-url property of an individual app (to display application logos on the landing page) now also support the file scheme (to be able to use local files as logos)
• ShinyProxy no longer fails if shiny.proxy.cert-path is missing
• improved handling of failed app starts

1.0.1

• fix security issue when using proxy urls directly
• fix for starttls error when TLS already started
• remove Docker dependencies from .deb to allow for deployment of Docker on separate host

1.0.0

• new environment variable SHINYPROXY_USERGROUPS is made available to the Shiny apps and contains
  the group memberships of the authenticated user
• add support for LDAP with StartTLS using property shiny.proxy.ldap.starttls
• new optional setting shiny.proxy.docker.container-protocol to configure the container protocol; if not set, it will be taken from the docker host url as specified in shiny.proxy.docker.url
• added animated loading feedback while Shiny app (i.e. container) is launching
• the logo-url property now also supports the file scheme (to allow for local logo files)
• fix for influxdb usage statistics logging when username contains whitespace
• allow JVM to exit if ShinyProxy cannot open its allocated port
• switch from deprecated simple proxy client to load-balanced client
• generate SHA-256 and MD5 checksums for all downloads