Remote Connection Options
Connects over HTTP(S) to a terminal-service deployment, authenticating with the OAuth2 client-credentials grant against tokenUrl - required, since Terminal.connect always needs a token to reach the terminal service.
Parameters
base URL of the terminal service, for example https://terminal-service.example.com.
full OAuth2 token endpoint to POST grant_type=client_credentials to, for example https://auth.example.com/realms/apa/protocol/openid-connect/token.
OAuth2 client id of the confidential client. See tokenUrl.
OAuth2 client secret of the confidential client. See tokenUrl.
optional tenant, sent as X-Tenant-ID.
when true, accepts any TLS certificate (including self-signed ones) for both the token request and the terminal's own calls - only meant for local/dev environments with a self-signed certificate (e.g. *.apa-dev.local); never enable this against a production terminal service, since it disables all certificate validation.
when true (the default), Terminal polls the terminal in the background once keepAliveInterval has passed without any other call, so a terminal that goes unreachable while idle is still noticed (moving Terminal.getState to TerminalState.DISCONNECTED) instead of only surfacing on the next real call. Any call made in the meantime resets the idle timer, so this is a no-op while transactions are already flowing frequently enough on their own.
how long the connection may sit idle before enableKeepAlive triggers a background keep-alive poll. Defaults to one minute.
Types
Fluent alternative to the constructor, for callers who prefer setting fields incrementally (for example when some values are only known conditionally). Equivalent to the constructor otherwise - neither is "the" supported way. Obtain one via RemoteConnectionOptions.builder.