1. URL Redirection: redirects incoming client requests to a different host/context
   This technique allows you to make a web address/context available under more than one URL address.
   It can be used for URL shortening, to prevent broken links, to allow multiple domain names to refer to a single Omniscope Mobile. (more info here)
   
   Host redirection
   For instance, the following configuration allows to redirect the client, that was navigating to "alpha.omniscope.me", to the different "https://omniscope.me" host.
   
   e.g. it redirects from "http://alpha.omniscope.me/folder/file.iok" to "https://omniscope.me/folder/file.iok"
   
   Context redirection
   Another example is to redirect requests to a particular context (e.g. link to a particular IOK file)
   Say that your server is serving at "http://server.domain" and you want to redirect "http://server.domain/dashboard" to the full link "http://server.domain/MyDefinitelyBeautifulDashboard.iok". The following configuration allow you to do so.
   
   e.g. it redirects from "http://server.domain/dashboard" to "http://server.domain/MyDefinitelyBeautifulDashboard.iok"
   
   Host and context redirection
   This example combines host and context redirection.
   Say that you server is serving at "http://alpha.omniscope.me" and you want to redirect the "/demo" context to a different host "https://demoserver/" and different context "/MyBeautifulDashboard.iok". Then use the following configuration
   
   It will redirect from "http://alpha.omniscope.me/demo" to "https://demoserver/MyBeautifulDashboard.iok".
   
   To redirect all incoming requests to a particular context regardless your server host/virtualhost name, then leave the VirtualHosts field empty.
   
   N.B. by specifying the Redirect from field you define which context has to be redirected.
   If you leave it blank then the URL redirection will be applied on all the incoming requests. In this case it is better if you perform redirection to a different host by specifying a full URL in the Redirect to field (e.g. "https://differentHost/pathTo/file.iok")
   Be aware that misconfiguration may create redirect loop error.
   
   
2. Redirect HTTP to HTTPS: redirects all incoming HTTP requests to HTTPS.
   If the HTTPS protocol is enabled, this option will configure your server to serve the content only through the HTTPS secured channel.

1. Configure security options as needed
   
2. Enable port forwarding on your external network firewall
   
3. Buy a domain name
   
4. Configure the domain to point to your firewall's external IP address
   
5. If using user logins, you should also buy an SSL certificate and configure HTTPS only access.
   

Permissions

• listDirectory : allow users to list existing files and subfolders
  
• downloadFile : allow users to download the IOK files
  
• viewInMobile : allow users to launch the Omniscope Mobile app for the existing IOK files
  
• fileManagement : allow users to upload IOK files, rename and delete resources, create new folders in the folder
  
• getStatic : allow users to get/access static resources from the folder, and to customise default styles (e.g. logo, icons, css files)
  
• viewServerState : allow users to view the server state through a monitoring page
  

User Credentials

• username : in clear text
  
• password : hash encrypted string using MD5 algorythm. As reference you can use this link to generate the hash.
  

folder.xml file structure

• Anonymous section
  The <anonymous> element describes the unauthenticated permissions, and is also used as default values for per-user permissions.
  Unauthenticated public access will be given these permissions. Any false/missing permissions will require authentication.
  
• Users section
  The <user> element describes the credentials and the permissions per user, and is made by the following elements/attributes:
  
  • Enabled : whether or not the user is enabled.
    
  • Credentials : the user username and password
    
  • Permissions: the user permissions that will override the anonymous ones
    
  
  

folder.xml example

Common use cases:

• Anonymous access not allowed, Admin user full permissions, Guest users browse and play IOK files
  <?xml version="1.0" encoding="UTF-8"?>
<mobilefolder>
<anonymous>
<permissions listDirectory="false" downloadFile="false" viewInMobile="false" fileManagement="false" getStatic="false" viewServerState="false"/>
</anonymous>
<users>
<user enabled="true">
<credentials>
<credentials username="admin" password="9aeb94180027a7081352cba05e6a3782" />
</credentials>
<permissions>
<permissions listDirectory="true" downloadFile="true" viewInMobile="true" fileManagement="true" getStatic="true" viewServerState="true" />
</permissions>
</user>
<user enabled="true">
<credentials>
<credentials username="guest" password="4aeb93180027a708186hy4505e6a6465" />
</credentials>
<permissions>
<permissions listDirectory="true" viewInMobile="true" getStatic="true" />
</permissions>
</user>
</users>
</mobilefolder>

  
• Anonymous can browse folders, no Admin user, Guest users browse and play IOK files
  <?xml version="1.0" encoding="UTF-8"?>
<mobilefolder>
<anonymous>
<permissions listDirectory="true" getStatic="true" />
</anonymous>
<users>
<user enabled="true">
<credentials>
<credentials username="guest" password="4aeb93180027a708186hy4505e6a6465" />
</credentials>
<permissions>
<permissions listDirectory="true" viewInMobile="true" getStatic="true" />
</permissions>
</user>
</users>
</mobilefolder>

  

• Both grouped and relational network types are supported.
• Node size, shape and colour.
• Line width and arrows.
• Label font and background.
  
• The "Circle" and "Best fit" layouts.