This repository should be used for testing Shiny applications that require authentication from external applications (e.g. Laravel platforms), without the need to setup the other application locally.
This application does the following:
- It includes an iframe that should render your main Shiny app. It points to the url given
- Clone this repository alongside the shiny application you wish to test.
- e.g. if your Shiny application is at
~\projects\your-shiny-app, clone this into~\projects\shiny-external-auth-tester: - in Powershell:
cd ~
git clone ...
- Create a ".sessions" folder in the same projects folder. This will be the folder that your main Shiny app should write session url files to.
You should now have the following folder structure, assuming you're working inside `~\projects':
- your-app\ -> contains your main Shiny app
- shiny-external-auth-tester\ -> contains this test app
- .sessions\ -> is empty (for now)
-
Run
renv::restore()to setup the library dependencies for this application. -
Create the .env file for this test shiny app. Copy the .env.example file and confirm it has the following variables:
MAIN_SHINY_URL="http://127.0.0.1:7008"
URL="http://127.0.0.1:7009"
- Ensure that the shiny application you wish to test also has a .env file if required. You will likely need to add the following variables to it:
LARAVEL_APP_URL=http://127.0.0.1:7009
URL=http://127.0.0.1:7008
To test your main app responds correctly to the authentication POST requests, you need to run both apps at the same time on different ports. Do the following:
- In one R session, run your main Shiny app on port 7008:
runApp(port=7008) - In another R session, run this app on port 7009:
runApp(port=7009).
To secure your main shiny app, it should be setup such that no private data is shown when running normally (http://127.0.0.1:7008), but all data is shown when running inside the iframe within this Shiny app (http://127.0.0.1:7009).