Binary packages are available at the releases page, or you can always build it from source. Mod authopenidc is provided in Debian as libapache2-mod-auth-openidc. To enable it, execute the following with root: a2enmod proxy_http It comes with most apache2 installs, but it is often disabled. If you don't already have apache2 installed, install it according to your platform and ensure that you have two modules: mod proxy and modauth_openidc. This will enable Apache to serve as a gatekeeper-a reverse proxy that only serves after authentication. We will use Apache as a gateway to our app using Auth0's tutorial. 1 Installing Apache and the OpenID Connect Module This ensures that we don't accidentally expose the open server to the entire Internet. When you have installed and configured Shiny and you're sure it works, modify your config file so it only serves to 127.0.0.1 (the local machine). Installing and Configuring Shinyįirst, follow the instructions to install and configure Shiny Server. This is also useful if you have a legacy web app with a username and password everyone shares or if you are hosting a server with static files you want to share. One of the easiest ways to add authentication to Shiny and, by extension, any unsecured web application, is to use Apache with Auth0 through the auth_openidc module. In that case, you likely won't want everyone on the Internet to be able to see your internal analytics, so you'll need to install and configure the authentication yourself. The open-source version of Shiny Server features no Authentication, and if it's open on Internet, it leaves your data exposed.

Aws shiny server