-
Deployment
-
Administrative Guide
- Settings
- Sharing Files
- Authentication Mechanisms
- Audit
- Backup & Restore
- Search Files using Index Service
- SSO Configuration For AdminConsole
- Admin Roles
- Access Restriction with IP Address
- System Requirements
-
- 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
-
- Articles coming soon
-
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
S3 file sharing with Okta Users
Nirvashare has made it easier to share files from S3 object storages like AWS S3, DigitalOcean space, Linode, Vultr, etc with users belonging to external identity providers like Okta.In addition to this,Nirvashare also supports numerous other identity providers such as Azure Active Directory, Google workspace, Keycloak, etc. In this step by step guide,let us understand the method used to integrate Okta identity provider with Nirvashare to share and access files from S3 object storage. Here, it is important to note that,steps will remain more or less same while integrating with other identity providers as well.
Prerequisite
As a prerequisite for S3 file sharing with Okta users, you should install Nirvashare and configure its storage.You can follow the procedure for installation provided in any one of the following documents
The below document can aid you in configuring storage which can vary based on your choice of cloud storage
Login Profile Creation
In order to enable SSO with Okta identity provider, a login profile in NirvaShare should be created. The below mentioned steps will help you to create one.
- Login as an administrator into admin console of NirvaShare.
- On the left menu of the admin console click on login profiles
- Click on CREATE located in the top right corner of admin profile
- Provide a name for the title.
- For the Authentication,select External Single Sign On (SSO) and click on CREATE
- This will create a new Login Profile.

Note –Refer to Access restriction with IP Address to restrict access to only certain white listed IP address or a range
ACS and Entity ID
Further, while configuring Okta, you will require ACS and Entity Id URL, hence please make a note of these two URLs. These two URLs can be obtained by editing the new created login profile.

Okta Configuration
To integrate NirvaShare with Okta, a SAML application has to be created in Okta and the steps mentioned below should be followed
- Sign into Okta console as an administrator.
- Now go to Applications at the left side of the menu and click on Applications in the Okta console.
- Click on Create App Integration.
- In the pop-up page for Sign-In method, select SAML 2.0.
- Click on Next
Note – For more information, you can also refer to Okta Documentation for further reference.

- Give the app a name of your choice
- Select a logo (optional)
- Click on Next

- The next screen will ask for ACS and Entity Id URLs of Nirvashare obtained in the previous section.
- Enter ACS URL in the Single Sign On URL field and select the option to ‘Use this for Recipient URL and Destination URL’.
- Enter the Entity Id URL into the Audience URL field, this URL contains the SAML metadata of the NirvaShare login profile.

- Leave the attribute statements (optional) field blank
- Scroll to Group attribute statements
- Type in member in the Name field, choose basic in the Name format drop down, Matches regex in the filter drop down and key in “ .* ” in the filter field
- Click on Next to move onto the feedback section.

- In the feedback section, select the option that says ” I’m a Okta customer adding an internal app ” and also check the option This is an internal app that we have created.
- Now click on Finish

- Click on the Assignment tab in the next screen
- Assign one or more users to this app by clicking on Assign drop down

- In the next step,click on Sign On tab
- Now if you click on Copy, you will get the link of Okta metadata URL

- Go to a new browser tab and open the Okta metadata URL
- Locally save the XML by right clicking on the URL, this external IDP metadata file will have to be updated in NirvaShare Login Profile.
Updating Login Profile with Okta SAML Metadata
The SAML metadata file obtained from the above process from Okta should be updated in the login profile in NirvaShare. Here we have listed the steps to do it.
- Login as an administrator into admin console of NirvaShare
- Go to left menu of admin console and click on Login profiles.
- Edit the Login profile that we created earlier.
- In the Authentication section click on the browse button and select the metadata file for the External IDP SAML Metadata section.
- Click on Update.

Shares
After all these steps, we can finally use SSO with Okta. For this let us create a folder share and enable SSO. Refer to the document mentioned below to create a new share from Storage. But remember to select the login profile we created in the above section during the process of sharing. You can create one or more shares as well and assign the same login profile.
Verification
- Go to the admin console, right click on the login profile that we created and choose Copy Shareable Link.
- Open the link in a browser in order to redirect Okta for SSO.
Once you complete the authentication, you can access Shares assigned to the login profile.
