Users access prerequisites
Fime Test Factory (FTF) is a SAAS application.
The following Web Browser have been tested :
- Google Chrome version 99+
- Mozilla Firefox version 90+
JavaScript and cookies
JavaScript must be activated, and session cookies accepted to use Fime Test Factory.
As data privacy is key for us, Fime only use cooking for technical needs (Maintain sessions, authentication between the different platform components, ...)
Fime connector
Some test suites needs to setup Fime connector on User desktop.
Fime Connector is a desktop app, driven by an FTF tool to capture and analyze frame coming from tested sample. Refer to Fime connector documentation for further information.
Firewall Prerequisites
This section describes IT prerequisites to be able to smoothly run FTF.
The target audience for this section is user's IT team.
Region endpoints for FTF
|
Regions |
Ip adresses |
Comment |
Europa (Default) | 149.202.145.41 | Portal + Tools by default |
|
India |
3.108.86.217 |
Tools for Indian customers |
|
Japan |
52.68.247.121 |
Tools for Asian and Australian customers |
|
America |
3.97.86.37 |
Tools for american customer |
Communication protocols
All communication with Fime Test Factory is encrypted and secured.
HTTPS ( with a TLS 1.3+ certificate)
Encrypted Web sockets is required (HTTPS Upgrade in WS)
HTTPS is used for Portal and tools, and Web sockets for tools and connectors.
Domains
All tools are accessed through the following domains (https:// & wss://):
Portal.fime.cloud (Portal URL + Static content)
*.eu-central-1a.fime.cloud (Tool URL)
*.ap-south-1a.fime.cloud (Tool URL)
*.ap-northeast-1a.fime.cloud (Tool URL)
*.ca-central-1a.fime.cloud (Tool URL)
Or their respective counterparts for white-labelling versions.
Applications in FTF use Angular framework.
So browser needs also to access to the following resources :
-
fonts.gstatic.com
-
fonts.googleapis.com
Email communication
Platform also used email addresses for communication
and notification.
The following email address must be declared as approved sender:
(Or their counter-part for White label)
White label deployment
FTF can be deployed as a White label application, in that case, some additional specific requirements are required as :
a domain name
a wildcard SSL certificate for this domain
an SMTP relay to manage email coming from the site