-
Deployment
-
Administrative Guide
-
- AWS S3 Storage Configuration using Access and Secret keys
- AWS S3 Storage Configuration using IAM role
- Google Storage Configuration using JSON Authentication Key
- Azure Blob/File Storage Configuration using Access Keys
- Backblaze B2 Storage Configuration using Access and Secret Keys
- DigitalOcean Storage Configuration using Access and Secret Keys
- Oracle Storage Configuration using Access and Secret Keys
- Wasabi Storage Configuration
-
-
Tutorials
- Quick Start
- AWS S3 File Sharing With Password Protection
- Google Cloud Storage Integration
- SSO for Admin Console using IAM Identity Center
- SSL and Load balancer for NirvaShare on AWS
- SSO for AdminConsole using Azure ActiveDirectory
- SSL Using Nginx Proxy Manager
- How to Share and Manage File Access from AWS S3, Azure Blob with Salesforce Users
- Configure SSO for Admin Console using Google Workspace as Identity Provider
- Share Azure Blob Files with ActiveDirectory Users using SSO
- S3 File Sharing with Okta Users
-
Troubleshoot
SSL and Domain Names
After successful installation, File/Folder Shares can be tested without domain name and SSL certificates but however for production, you will require one.
Domain Names
NirvaShare requires two domains, one for admin console app and the other one for user facing share service app or user app. It would be better to have two sub domains something like below. You can use any name of your choice.
- https://admin.yourdomain.com
- https://share.yourdomain.com
Note: NirvaShare services of Admin console uses port 8080 and user app uses port 8081
SSL Certificates
For a certificate, make sure to pick one of the below approach.
- Obtain CA certificate for your domain from external authority.
- Use certbot with LetsEncrypt for free certificate.
Since there are multiple ways to configure SSL, chose any one of the option from the following.
Option 1
Use Nginx Proxy Manager service. This is pretty easy to configure and for steps, please refer to SSL with Nginx Proxy Manager
Option 2
Using load balancer. Depending on the cloud platform, you can configure load balancer to have domain and SSL certificates. Refer to respective cloud platform documentation for more information. Below is the documentation for SSL in AWS
Option 3
There are many other means of configuring SSL using servers like Apache2, Jetty, etc. Please check respective websites for more information.
Further any help or support needed in configuration, please contact us at HERE, we will be happy to assist you.