Information to Collect for a New D-Direct App

The key information to collect from a customer to set up a D-Direct app is as follows:

Confirm with the customer that ports 80 and 443 (TCP) are sufficient to have open, and that no other ports need to be opened.
Client domain - this is the domain that is being requested from the client device
endpoint - this must either be a static IP address or a domain. If it's a domain, then it must be different than the client domain.
Proxy protocol support - From experience, the customer typically does not need this turned on, but in certain cases the customer needs to be able to see the client IP address. We can pass this IP address in the proxy protocol header. If this is turned on, then the customer must support proxy protocol on the endpoint.
Standard vs high availability - This is an option that usually wouldn't be mentioned as an option to the customer, since the vast majority of customers are okay with using the "standard" version of D-Direct. "High availability" would only ever be used for a customer like a bank who has the need for a higher SLA, eg. 99.99% uptime. This is the scenario where we could provide a high availability D-Direct to a customer.

Last updated 1 month ago

The key information to collect from a customer to set up a D-Direct app is as follows:

Confirm with the customer that ports 80 and 443 (TCP) are sufficient to have open, and that no other ports need to be opened.
Client domain - this is the domain that is being requested from the client device
endpoint - this must either be a static IP address or a domain. If it's a domain, then it must be different than the client domain.
Proxy protocol support - From experience, the customer typically does not need this turned on, but in certain cases the customer needs to be able to see the client IP address. We can pass this IP address in the proxy protocol header. If this is turned on, then the customer must support proxy protocol on the endpoint.
Standard vs high availability - This is an option that usually wouldn't be mentioned as an option to the customer, since the vast majority of customers are okay with using the "standard" version of D-Direct. "High availability" would only ever be used for a customer like a bank who has the need for a higher SLA, eg. 99.99% uptime. This is the scenario where we could provide a high availability D-Direct to a customer.

Last updated 1 month ago