2c8 Client for Modeling Tool / Lite
2c8 Modeling Tool and Lite are the client software installed on the users computer. Can be used with or without a server.
Operating System: Windows 7, 8, 8.1, 10 / 11 *
RAM: Minimum 2GB
HDD: Minimum 1 GB free disk space
*Only 64 bit versions are supported.
Kommunikation:
Below outbound communication needs to be allowed.
Destination server | Protocol/Port | Purpose |
lic.2c8.com | HTTPS/443 | Download program resources, including automatic program updates |
extension.2c8.com | HTTPS/443 | Installation and update of plugins |
www.2c8.com | HTTPS/443 | News feed by RSS |
idp.2c8.com | HTTPS/443 | Authentication of users |
as.2c8.com | HTTPS/443 | Authorization of users to run the application and to authorize to access a server |
"servername".yourdomain.com / "servername".2c8.com | HTTPS/*/443 | If you are working against a server you need to allow access against that. For self hosted server you decide port and hostname. For servers hosted by 2c8, port is always 443 |
The client is not build for or tested to be run on a Terminal server / Citrix environments. For that reason we have no official support for such installation, but we have customers that run it successfully
2c8 server (customer hosted)
For customer hosted server, below is needed:
- Appliction server - Here the Java EE application Payara Glassfish is installed
- Database server - For database used by Payara
These to can be on the same or separate server instances.
Operating System: Windows Server 2016 or later
Databasserver: MSSQL 2016 or later, or MySQL 5.5 or later
RAM: Minimum 2 GB
CPU: Minimum 2 CPU core
HDD: Minimum 5 GB free disk space
Network bandwidth: Minimum 10 Mbit (Recommended 100 Mbit)
Communication:
Below outgoint communication needs to be allowed
Destination server | Protocol/Port | Purpose |
idp.2c8.com | HTTPS/443 | Authentication of application server to access as.2c8.com |
as.2c8.com | HTTPS/443 | The list of user that are allowed to connect to the server is stored here. This is synced to the server by a call to this URL |
Below incoming communication needs to be allowed
Source | Protocol/Port | Purpose |
Client computers | HTTPS/Port of your choice | To allow the client to access server |
SSL certificate: We only allow https traffic from client to server, which means you need a SSL certificate. More about this here.
Outgoing email(Not mandatory): To enable the application to send email notification you need to configure SMTP. More about this here.
Single sign-on(SSO)
- Version 2024.1 or newer
- An agreement of the type Subscription or Enterprise
- An Identity Provider that supports SAML 2.0
- Launcher version of the client. Does not work with fixed client versions
The solution is only tested with Microsoft Azure Entra ID and Microsoft Active Directory Federation Services, but likely work with other identity providers as well. No support can be provided for other identity providers though.
Read more about the configuration here.
AD-Connector
The AD connector is an application that is installed on a Windows server in you IT environment and that has access to you AD server over LDAP/LDAPS. The application can also be installed directly on you AD server.
Prerequisites:
- Version 2024.1 or newer
- An agreement of the type Subscription or Enterprise
- A Microsoft Active Directory with LDAP/LDAPS enabled.
- For use with Entra ID, Entra ID Domain Services needs to be installed.
Note! 2c8 does not offer any support on how do setup AD, Domain services or how to enable LDAP/LDAPS.
Server system requirements:
Operating System: Windows Server 2016 or later
RAM: Minimum 2 GB
CPU: Minimum 2 CPU-kärnor
HDD: Minimum 5 GB free space
Network bandwidth: Minimum 10 Mbit (Recommended 100 Mbit)
Communication
Below outgoing communication needs to be allowed
Destination server | Protocol/Port | Purpose |
idp.2c8.com | HTTPS/443 | Authentication |
lic.2c8.com | HTTPS/443 | Authorization |
"your-ad-server.domain.com" | LDAP/389 or LDAPS/636 | Used to sync users |
SSL certificate:
- An SSL certificate for the server host name. Used to access AD connector config over HTTPS. More info about the requirements here.
- If u wish to use LDAPS to connect to your AD, you need to export a certificate from your LDAP setup on AD server
Service account:
A user account used by AD Connector to authenticate when connecting to your AD over LDAP/LDAPS
Comments
0 comments
Please sign in to leave a comment.