Hello @Thulasidhar-Siva,
DotNet Client
On the topic of dotnet clients, there’s documentation here:
Even though this says C# in our docs, because this runs on CLR VM (Common Language Runtime), this should work with any language on dotnet platform.
GoDaddy Cert/Key
As far as using external certificates, i.e. GoDaddy. The easiest approach for HTTPS wold be to add the certificate to the load balancer and terminate TLS there.
For HTTPS or GRPC (h2) directly to the Dgraph Alpha service w/o terminating at the load balancer, this is how you might be able to do this. You definitely would have to use --tls_use_system_ca when starting Dgraph Alpha. If you can supply the ca.crt and **ca.key**, and generate the web server cert/key with GoDaddy and save these as node.crt and node.key, then this should work.
However, if you do not have the ca.crt and ca.key (which is understandable, as GoDaddy wouldn’t give this out if it is a public trusted cert/key), then you need to generate cert/key saved as node.crt and node.key. You may have to generate a ca.crt and ca.key with dgraph cert command to put in the tls directory, but with --tls_use_system_ca, Dgraph Alpha will check the against public CA certs/keys like GoDaddy.
Lastly, I wanted to mention that the incoming requests with TLS, the client has to use a FQDN that is specified in the certificate or session will be rejected. Thus you will have to make sure than when the client makes a request to the endpoint, the endpoint matches the configured FQDN in the certificate. This can be done when testing out the solution, such as:
- A or CNAME record to the endpoint configured in a DNS server
- client configuration, e.g.
/etc/hosts, with the endpoint and desired FQDN - add
Hosts <FQDN>in header when making request -
curl and adding
--resolve <FQDN>:port https://<endpoint>command line flag