When installing the Trust1Connector you will have a launcher executable. This executable takes care of a couple of things;
Starting the Trust1Connector
Stopping the Trust1Connector
Migration (makes sure file-exchange is kept between installation)
Below you can find an output of the flags and options that can be used;
most used variables to just managing the Connector are --stop--restart--env [env]. The other flags are used to customize the Connector
t1c-launch.exe
Trust1Connectorlauncher3.8.6Trust1Team<development@trust1team.com>LauncherfortheTrust1ConnectorUSAGE:t1c-launch [FLAGS] [OPTIONS] [ARGS]FLAGS:-d,--debugEnablesDebugmode (additional endpointsex.'/decrypt'available)--ds.regEnablestheuseoftheDistributionserviceRegistry (only inonlinemode) -ds.server_addressMUSTbeprovided-thereisnodefaultDS --enable.curl Enables the use of CURL for DS communication (enabling NTLM or SSPI on Windows). Fallback on
regularDScommunication.--enable.jwtEnablestheuseofJWTvalidationmiddlewareontheAPIserver.NousecasescanbeperformedwithoutsendingavalidJWTfromtheconsumerrequest.TheJWTmustbeissuedbytheconfiguredDS.-fEnablestheuseforthefilelogger.--fix.dns.rebindWhenadded,theAPIwillverifytheDNSonthelocaldevice,whenfailing:trytoupdatehostfile,askinguserforadminpermissions--fix.ssl.directWhenadded,theAPIwillcheckthevalidityoftheSSLcertificateonstartup.-h,--helpPrintshelpinformation--httpRunstheAPIandRegistry (if enabled) in HTTP mode (nomTLS)--migrateExecutesthemigratefunctionalitywhichwillcleanupthecurrentinstallation--nofilexWritesamarkerfile (nofilex.marker) to Program Files folder, denoting the inactivation ofthefileexchangemoduleinsharedenvironment -q Overrides file log and uses a console subscriber instead (tokio-console) to view the tracing
logsindetail.--remove-launchdRemovesthelaunchdconfigurationfromthesystem (Only onMacOS)--restartRestarttheTrust1Connector--silentsilentmodewhichwillnothidetheconsolewindow--skip-killSkipskillingtheprocessesuponstart|restart|stop|migrate-z,--standaloneDisablesRegistry,runsonlyinstandalonemodewithoutsupportformulti-hostsessions--stopStoptherunninginstance-V,--versionPrintsversioninformationOPTIONS:--api.bin_name<api.bin_name>OverwritethedefaultT1Capibinaryfile.-p,--api.port<rnd:{10000-65535}>SetstheAPIport--api.server_address<localhost>SetstheAPIURI.--cors<cors>Provideabase64encode,comma-separatedlistofcorsoriginstobeprovidedonstartup.WhenusingaDistributionService,theCORSisoverwrittenbytheDSconfiguration.--dialogs.timeout<60>Defaulttimeoutfordialogs (PIN, filechooser,dirchooserorotheronWindowsandOSX), override on APIperusecasepossible--dns<t1c.t1t.io>SetsDNSfortheT1C (recommended thattheotherserveraddressesareseton [localhost]).--ds.api.key<ds.api.key>SettheLicensekey,bydefaultusingthepackagedkey.ThisisneededwhenoperatingwithaDSforkeyexchange--ds.cycle<28800>AmountofsecondtosyncwiththeDistributionService (8 hours). Upon install, restart and init DS syncwillbetriggered.--ds.server_address<ds.t1t.io>ActivatedONLINEmodeusinggivenDistributionServiceHost.Ifnotgiven,theT1C-APIrunsinOFFLINEmode--env<prod>DefinestheenvironmentwheretheTrust1Connectormustrun [possible values:dev,acc,prod]--grpc.port<rnd:{10000-65535}>SetstheGRPCport.--grpc.server_address<localhost>SetstheGRPCURI.-A,--grpc.server_bin_name<t1c-sandbox-service>ThenameofthebinaryexecutablefortheSandbox--launcher.bin_name<t1c-launch>OverwritethedefaultT1CLauncherbinaryfile.BydefaultforOSX:launchctl,WIN:t1c-launch.exe,LINUX:t1c-launch.ThisoptiononlyworksforWindowsandLinuxOSasOSXisusingbydefaultlaunchctl.--log<log>Logfilter,followingtokiotracingcratesyntax.Forexample:t1c_rust_api=info|warn|debug.--ntlm.proxy_address<ntlm.proxy_address>SetstheIPAddressoftheNTLMproxyserver.Disabledbydefault--payload.size<2000> The amount in kilobyte of allowed body payload size. By default 2000 kilobyte: body payload of 2MB accepted.
Maximumvalue:50000 (50MB)-t,--reg.cycle<60>Amountofsecondtosyncwiththeregistryprocess-x,--reg.port<51883>SetstheRegistryport (fixed percustomer).--reg.server_address<localhost>SetstheRegistryURI.-C,--reg.server_bin_name<t1c-reg>ThenameofthebinaryexecutablefortheRegistry--root.api.path<root.api.path>Settherootfolderfortheapi. --root.launcher.path <root.launcher.path> Set the root folder for the launcher, by default uses user.path.
-w,--root.reg.path<root.reg.path>Settherootfolderfortheregistry.-r,--root.sandbox.path<root.sandbox.path>Settherootfolderforthesandbox.-U,--user.path<user.path>Setthefolderforuserfilesforthetrust1team-launch.Thedevicepem/cert,logfilesandfileexchangemappingsaredirectlyavailableinthisfolder.--workers<2> Amount of HTTP workers for multi-threading. Mostly the number of logical CPUs in a system, by default is set
to2.ARGS:<external.storage> Enablestheuseofexternalstorageforthefileexchangemodule.ThisisonlyavailableonWindowsandMacOSX.<external.storage.overwrite> Overwritesthegeneratedfilesforeachcardreading.<external.storage.format> Definesthecarddumpformat (xml|json)<external.storage.poll> Amountofsecondstopollfornewcarddumps.<external.storage.path> Folderlocationwherethefilemustbecreated (file containsthecardinformationfollowingthechosenformat
Start the Trust1Connector
To start the trust1connector you can execute the following, be aware that the command option depends on which environment you have installed. Below you can find in comments which environment will be triggered.
When the start command is executed the Trust1Connector will first stop the running instances before starting.
Running the launcher as a different environment from which you have installed will not work
When installing the Trust1Connector you will have a launcher executable. This executable takes care of a couple of things;
Starting the Trust1Connector
Stopping the Trust1Connector
Migration (makes sure file-exchange is kept between installation)
MacOS launcher has the same functionality but works differently in the background. It will use launchd to start/run the Connector.
Below you can find an output of the flags and options that can be used;
most used variables to just managing the Connector are --stop--restart--env [env]. The other flags are used to customize the Connector
t1c-launch.exe
USAGE:t1c-launch [FLAGS] [OPTIONS]FLAGS:-d,--debugEnablesDebugmode (additional endpointsex.'/decrypt'available)--ds.regEnablestheuseoftheDistributionserviceRegistry (only inonlinemode) -ds.server_addressMUSTbeprovided-thereisnodefaultDS --enable.curl Enables the use of CURL for DS communication (enabling NTLM or SSPI on Windows). Fallback on
regularDScommunication.--enable.jwtEnablestheuseofJWTvalidationmiddlewareontheAPIserver.NousecasescanbeperformedwithoutsendingavalidJWTfromtheconsumerrequest.TheJWTmustbeissuedbytheconfiguredDS.-h,--helpPrintshelpinformation--migrateExecutesthemigratefunctionalitywhichwillcleanupthecurrentinstallation--nofilexWritesamarkerfile (nofilex.marker) to Program Files folder, denoting the inactivation ofthefileexchangemoduleinsharedenvironment--remove-launchdRemovesthelaunchdconfigurationfromthesystem (Only onMacOS)--restartRestarttheTrust1Connector--silentsilentmodewhichwillnothidetheconsolewindow--skip-killSkipskillingtheprocessesuponstart|restart|stop|migrate-z,--standaloneDisablesRegistry,runsonlyinstandalonemodewithoutsupportformulti-hostsessions--stopStoptherunninginstance-V,--versionPrintsversioninformationOPTIONS:--api.bin_name<api.bin_name>OverwritethedefaultT1Capibinaryfile.-p,--api.port<rnd:{10000-65535}>SetstheAPIport--cors<cors>Provideabase64encode,comma-separatedlistofcorsoriginstobeprovidedonstartup.WhenusingaDistributionService,theCORSisoverwrittenbytheDSconfiguration.--dialogs.timeout<60>Defaulttimeoutfordialogs (PIN, filechooser,dirchooserorotheronWindowsandOSX), override on APIperusecasepossible--ds.api.key<ds.api.key>SettheLicensekey,bydefaultusingthepackagedkey.ThisisneededwhenoperatingwithaDSforkeyexchange--ds.cycle<28800>AmountofsecondtosyncwiththeDistributionService (8 hours). Upon install, restart and init DS syncwillbetriggered.--ds.server_address<ds.t1t.io>ActivatedONLINEmodeusinggivenDistributionServiceHost.Ifnotgiven,theT1C-APIrunsinOFFLINEmode--env<prod>DefinestheenvironmentwheretheTrust1Connectormustrun [possible values:dev,acc,prod]-g,--grpc.port<rnd:{10000-65535}>SetstheGRPCport.-A,--grpc.server_bin_name<t1c-sandbox-service>ThenameofthebinaryexecutablefortheSandbox--launcher.bin_name<t1c-launch>OverwritethedefaultT1CLauncherbinaryfile.BydefaultforOSX:launchctl,WIN:t1c-launch.exe,LINUX:t1c-launch.ThisoptiononlyworksforWindowsandLinuxOSasOSXisusingbydefaultlaunchctl.--ntlm.proxy_address<ntlm.proxy_address>SetstheIPAddressoftheNTLMproxyserver.Disabledbydefault--payload.size<2000> The amount in kilobyte of allowed body payload size. By default 2000 kilobyte: body payload of 2MB accepted.
Maximumvalue:50000 (50MB)-t,--reg.cycle<60>Amountofsecondtosyncwiththeregistryprocess-x,--reg.port<51883>SetstheRegistryport (fixed percustomer).-C,--reg.server_bin_name<t1c-reg>ThenameofthebinaryexecutablefortheRegistry--root.api.path<root.api.path>Settherootfolderfortheapi. --root.launcher.path <root.launcher.path> Set the root folder for the launcher, by default uses user.path.
-w,--root.reg.path<root.reg.path>Settherootfolderfortheregistry.-r,--root.sandbox.path<root.sandbox.path>Settherootfolderforthesandbox.-U,--user.path<user.path>Setthefolderforuserfilesforthetrust1team-launch.Thedevicepem/cert,logfilesandfileexchangemappingsaredirectlyavailableinthisfolder.--workers<2> Amount of HTTP workers for multi-threading. Mostly the number of logical CPUs in a system, by default is set
to2.
Start the Trust1Connector
To start the trust1connector you can execute the following, be aware that the command option depends on which environment you have installed. Below you can find in comments which environment will be triggered.
When the start command is executed the Trust1Connector will first stop the running instances before starting.
Running the launcher as a different environment from which you have installed will not work
Check if the Trust1Connector is running via launchd
If you want to check if the launchd API is running you can do the following;
# list the launchd instances and then grep the t1tlaunchctllist|grept1t# The following should have a similar output, the 2nd number will be a different number when the Trust1Connector is not starting correctly
648320com.t1t.t1c.api
The output will have 3 parameters;
PID of the running instance, will be 0 if not running
Error code of the instance, will be 0 if none
name of the launchd program
If you have an error code and the PID is 0, please contact support.
An error code can occur and will remain visible in the launchctl command. As long as the instance has a valid PID it means the Trust1Connector is running as expected.
That error code can indicate a crash from the past.