secure_server

A Shiny server function (e.g <code>function(input, output, session) {}</code>)

server

Either <code>NULL</code>, the default, or a Shiny module server containing your custom
sign in server logic.

custom_sign_in_server

Either <code>NULL</code>, the default, or a Shiny module server function containing your custom admin
server functionality.

custom_admin_server

argument to pass to the Shiny <code>session$allowReconnect()</code> function. Defaults to
<code>FALSE</code>. Set to <code>TRUE</code> to allow reconnect with shiny-server and RStudio Connect. Set to <code>"force"</code>
for local testing. See <a href="https://shiny.rstudio.com/articles/reconnecting.html">https://shiny.rstudio.com/articles/reconnecting.html</a> for more information.

allow_reconnect

whether or not to override the <code>session$user</code> with the polished
<code>session$userData$user</code> user. By default this is now set to <code>TRUE</code>, but if you are
using a hosting option that uses the <code>session$user</code> (e.g. RStudio Connect), then you
may want to set this to FALSE. The polished user can always be found at <code>session$userData$user()</code>.

override_user

This function is used to secure your Shiny app's server function. Make sure to pass
your Shiny app's server function as the first argument to <code>secure_server()</code> at
the bottom of your Shiny app's <code>server.R</code> file.

Easily add modern authentication and user administration to your 'shiny' apps.
Customize user sign in and registration pages to match your brand.  Control who can
access one or more of your 'shiny' apps. Also, deploy & host your apps with Polished Hosting.

Andy Merlino

polished

Authentication, User Administration, and Hosting for 'shiny'
Apps

Patrick Howard

Jimmy Briggs

secure_server function

<dl><dt>server</dt>
<dd>A Shiny server function (e.g <code>function(input, output, session) {}</code>)</dd>
<dt>custom_sign_in_server</dt>
<dd>Either <code>NULL</code>, the default, or a Shiny module server containing your custom
sign in server logic.</dd>
<dt>custom_admin_server</dt>
<dd>Either <code>NULL</code>, the default, or a Shiny module server function containing your custom admin
server functionality.</dd>
<dt>allow_reconnect</dt>
<dd>argument to pass to the Shiny <code>session$allowReconnect()</code> function. Defaults to
<code>FALSE</code>. Set to <code>TRUE</code> to allow reconnect with shiny-server and RStudio Connect. Set to <code>"force"</code>
for local testing. See <a href="https://shiny.rstudio.com/articles/reconnecting.html">https://shiny.rstudio.com/articles/reconnecting.html</a> for more information.</dd>
<dt>override_user</dt>
<dd>whether or not to override the <code>session$user</code> with the polished
<code>session$userData$user</code> user. By default this is now set to <code>TRUE</code>, but if you are
using a hosting option that uses the <code>session$user</code> (e.g. RStudio Connect), then you
may want to set this to FALSE. The polished user can always be found at <code>session$userData$user()</code>.</dd></dl>

Arguments

Secure your Shiny app's server — secure_server

<dl>

<dt>server</dt>
<dd>A Shiny server function (e.g <code>function(input, output, session) {}</code>)</dd>


<dt>custom_sign_in_server</dt>
<dd>Either <code>NULL</code>, the default, or a Shiny module server containing your custom
sign in server logic.</dd>


<dt>custom_admin_server</dt>
<dd>Either <code>NULL</code>, the default, or a Shiny module server function containing your custom admin
server functionality.</dd>


<dt>allow_reconnect</dt>
<dd>argument to pass to the Shiny <code>session$allowReconnect()</code> function. Defaults to
<code>FALSE</code>. Set to <code>TRUE</code> to allow reconnect with shiny-server and RStudio Connect. Set to <code>"force"</code>
for local testing. See <a href='https://shiny.rstudio.com/articles/reconnecting.html'>https://shiny.rstudio.com/articles/reconnecting.html</a> for more information.</dd>


<dt>override_user</dt>
<dd>whether or not to override the <code>session$user</code> with the polished
<code>session$userData$user</code> user. By default this is now set to <code>TRUE</code>, but if you are
using a hosting option that uses the <code>session$user</code> (e.g. RStudio Connect), then you
may want to set this to FALSE. The polished user can always be found at <code>session$userData$user()</code>.</dd>

</dl>

secure_server: Secure your Shiny app's server

Description

Usage

Arguments