Issue
When attempting to bypass the Posit Workbench login page using automated authentication methods (like those commonly used with Open OnDemand), users may encounter authentication failures or be unable to skip the login screen entirely.
Description
While it's possible to bypass the login page for open-source RStudio Server using custom authentication methods, Posit Workbench has specific limitations and requirements that prevent certain authentication bypass scenarios:
- The auth-none setting, which allows bypassing authentication, is not compatible with Launcher-dependent features like VSCode and JupyterLab sessions.
- Launcher requires root user authentication, making it incompatible with single-user mode configurations.
- Attempts to pass pre-generated passwords may result in decryption errors due to Workbench's enhanced security features.
Solution
For environments requiring VSCode or JupyterLab sessions along with authentication bypass, consider the following approaches:
- Implement proxied authentication instead of trying to bypass the login page completely.
- Use PAM authentication with appropriate configuration if user state persistence is required.
- For environments where VSCode and JupyterLab are not needed, auth-none can be configured following the documentation at Server Permissions.
- Consider implementing Single Sign-On (SSO) through supported authentication providers if seamless access is required.
Note: When choosing an authentication method, consider these factors:
- Whether users need persistent home directories.
- Which IDE features are required (RStudio, VSCode, JupyterLab).
- Security requirements and compliance considerations.
- User state preservation requirements.
If you're still having issues, you can reach out to Support by opening a ticket here.