Difference between revisions of "Fusion Security Manager Install"
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[Category:FSM_Install]] | [[Category:FSM_Install]] | ||
| − | + | To install the Fusion Security Manager (FSM), the recommended approach is to host FSM on the same domain as your Fusion Registry, for example if your Registry is accessed via https://FusionRegistry.yourorg.com then FSM could be accessed via https://FusionSecurityManager.yourorg.com, this will eliminate any potential [https://en.wikipedia.org/wiki/Cross-origin_resource_sharing CORS] issues. | |
| − | To install the Fusion Security Manager (FSM), the recommended approach is to host | ||
If your Fusion Registry is hosted via Apache Tomcat, then you can simply copy and paste the Fusion Security Manager folder into the webapps folder of tomcat. Whatever your folder is called that has FSM will be what goes in your URL of the web browser, for example Tomcat/webapps/FusionSecurityManager will be accessed via http(s)//localhost:8080/FusionSecurityManager. FSM can be hosted on any server capable of hosting HTML and JavaScript, it does not need to be Apache Tomcat. | If your Fusion Registry is hosted via Apache Tomcat, then you can simply copy and paste the Fusion Security Manager folder into the webapps folder of tomcat. Whatever your folder is called that has FSM will be what goes in your URL of the web browser, for example Tomcat/webapps/FusionSecurityManager will be accessed via http(s)//localhost:8080/FusionSecurityManager. FSM can be hosted on any server capable of hosting HTML and JavaScript, it does not need to be Apache Tomcat. | ||
| Line 12: | Line 11: | ||
# Open your web browser, and enter the appropriate URL | # Open your web browser, and enter the appropriate URL | ||
| − | [[File: | + | [[File:FSM-GUI.png|1000px]]<br> |
Latest revision as of 02:44, 6 October 2023
To install the Fusion Security Manager (FSM), the recommended approach is to host FSM on the same domain as your Fusion Registry, for example if your Registry is accessed via https://FusionRegistry.yourorg.com then FSM could be accessed via https://FusionSecurityManager.yourorg.com, this will eliminate any potential CORS issues.
If your Fusion Registry is hosted via Apache Tomcat, then you can simply copy and paste the Fusion Security Manager folder into the webapps folder of tomcat. Whatever your folder is called that has FSM will be what goes in your URL of the web browser, for example Tomcat/webapps/FusionSecurityManager will be accessed via http(s)//localhost:8080/FusionSecurityManager. FSM can be hosted on any server capable of hosting HTML and JavaScript, it does not need to be Apache Tomcat.
Installation Steps
- Copy the Fusion Security Manager folder to your web application server (example Apache or Tomcat)
- Configure FSM using a text editor or JSON editor such as Brackets
- Configure Fusion Security Manager to ensure the target audience is able to see appropriate datasets. More information
- Open your web browser, and enter the appropriate URL
