For some modules, we have Requirements that are provided on this page. Please verify that all information are available in order to successfully activate the module.
Mailserver
Outgoing
For Outgoing Mails, the following information is needed:
- SMTP Host (eg mailhost.fqdn.com )
- SMTP Port (eg 25)
- TLS Required? (Yes/No)
- Authentification Required (Yes/No)
- Username (eg johndoe@yourcompany.com)
- Password
- Which sending Mailadresse can be used (eg system@yourcompany.com)
Incoming
If signalByMailReply is used (Mail interaction with an instance) the following information is needed:
- Protocol (IMAP, POP3, IMAPS, POP3S)
- Port (eg 993)
- Username (eg johndoe@yourcompany.com)
- Password
- WebMail client URL (eg https://mailhost.fqdn.com/owa/)
SAML 2.0
Requirements:
HTTPS is required for SAML module
Signature is required for SAML module
In order to enable SAML Authentification, an Endpoint has to created which allows our application to request Assertions which contain User information. The Relaying Part Trust needs the following settings:
- Identifier (entity ID) (eg https://server.fqdn/sso-login/)
- Reply URL (eg https://server.fqdn/sso-login/)
- Signature is required
- Endpoints (ADFS Only)
- SAML Assertion Consumer
- POST
- Index 0
- Trusted URL → https://server.fqdn.com/sso-login/
- Claim Rules (ADFS Only)
- samAccountName as Name-ID
LDAP
If the users should only authenticate (users are not created automatically) against LDAP the following information is required
Authentification
- LDAP Host (eg fqdn.com )
- LDAP Port (eg 389)
- DNS Suffix (eg fqdn.com)
- LDAP Protocol (eg LDAPS)
- Authentification mechanism (eg simple)
- Certificate (if required)
If users should also be created automatically if they are added in LDAP the following information is required
Synchronization
- LDAP Host (eg fqdn.com)
- LDAP Port (eg 389)
- Base DN (eg dc=fqdn,dc=com)
- distinguishedName of Bind User (eg CN=system,OU=systemuser,DC=fqdn,DC=com)
- Password of Bind User
Single Group Synchronization
- Distinguished Name of a Group (eg CN=SYSTEM-User,OU=Software,DC=fqdn,DC=com)
Multiple Groups Synchronization
- Distinguished Name of a Organizational Unit with SYSTEM Groups (eg OU=SYSTEM-Groups,DC=fqdn,DC=com)
If a separate Organizational Unit is not possible an LDAP Filter has to be provided which selects all necessary groups.
CAS (Central Authentication Service)
- CAS Host (eg https://sso.fqdn.com/cas)
- Ticketidentifier (eg -cas)
Sharepoint
In order to use a Sharepoint Library as the DMS System in the system the following information and resources are needed:
- Connection Properties (Can be generated here → https://<tenant>.sharepoint.com/_layouts/15/appregnew.aspx )
- ClientID
- ClientSecret
- TenantId (Can be found here → https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Overview )
- HostName (eg 'https://mytimdocuments.sharepoint.com')
- Documentlibary to store files in (eg 'Shared Documents')
Also, some additional Columns have to added to the Library. All columns have to be of type "string" and values must not be edited by hand
- Name of a column to store ProcessInstanceID (eg 'processinstanceid')
- Name of a column to store ProcessInstanceName (eg 'processinstancename')
- Name of a column to store Document Comments (eg 'comment')
- Name of a column to store the use who uploaded the document (eg 'uploaduser')
- Name of a column to store the date when document was last uploaded (eg 'uploadedon')
- Name of a column to store internal Ids after a file was modified (eg 'originalfile ')