This example is a zitified cURL (cURLz) example. In part 1 of this example, a call will be made to an endpoint which is not on the overlay network. In part 2, a call is made to an endpoint that is on the overlay network.
This example demonstrates:
- Dialing a service
- an OpenZiti network. If you do not have one, you can use one of the quickstarts to set one up.
- OpenZiti CLI to create services and identities on the OpenZiti Network
Refer to the example README to build the SDK examples
These steps will configure the service using the OpenZiti CLI. In this example, the traffic starts on the overlay zero trust network and then is offloaded onto the underlay network.
At the end of these steps you will have created:
- a service called
web.endpoint - an identity to connect to (dial) the service
- the service config to connect the service to the overlay
- the service policies required to authorize the identities for bind and dial
Steps:
-
Log into OpenZiti. The host:port and username/password will vary depending on your network.
```bash ziti edge login localhost:1280 -u admin -p admin ``` -
Determine your edge router's name and populate this environment variable with it.
```bash ziti edge list edge-routers export ZITI_EDGE_ROUTER=<name-of-edge-router> ``` -
Run this script to create everything you need.
```bash echo Changing to build directory cd $ZITI_SDK_BUILD_DIR echo Create the service config ziti edge create config web.endpoint.hostv1 host.v1 '{"protocol":"tcp", "address":"www.google.com","port":443}' echo Create the service ziti edge create service web.endpoint --configs "web.endpoint.hostv1" echo Create an identity to make the dial request and enroll it ziti edge create identity user curlz -a clients -o curlz.jwt ziti edge enroll --jwt curlz.jwt echo Create service policies ziti edge create service-policy web.endpoint.dial Dial --service-roles "@web.endpoint" --identity-roles "#clients" ziti edge create service-policy web.endpoint.bind Bind --service-roles "@web.endpoint" --identity-roles "@${ZITI_EDGE_ROUTER}" echo Run policy advisor to check ziti edge policy-advisor services ``` -
Run the cURLz example for
web.endpoint```bash ./curlz https://web.endpoint curlz.json ```
The following is the output you'll see from the cURLz request to web.endpoint.
$ ./curlz https://web.endpoint curlz.json
<!doctype html><html itemscope="" itemtype="http://schema.org/WebPage" lang="en">
... <a lot of html code>
</body></html>These steps will utilize the service and identities created in simple-server to provide an example of using cURLz with a zitified endpoint. In this example, the traffic never leaves the zero trust overlay.
At the end of these steps you will have created:
- an identity to connect to (dial) the service
Steps:
-
Follow all steps in the simple-service example up to, and including, running the server but do not enroll the
simple-clientidentity with the Ziti Desktop Edge client. We will do that with the CLI for this example -
Open a new terminal and cd into the example build directory
```bash echo Changing to build directory cd $ZITI_SDK_BUILD_DIR ``` -
Run this script to create everything you need.
```bash echo Enroll the simple-client identity ziti edge enroll --jwt simple-client.jwt ``` -
Run the cURLz example for
simpleService```bash ./curlz http://simpleService simple-client.json ```
The following is the output you'll see from the cURLz request to simpleService.
$ ./curlz http://simpleService.ziti simple-client.json
Who are you?Done with the example? This script will remove everything created during setup.
ziti edge login localhost:1280 -u admin -p admin
echo Removing service policies
ziti edge delete service-policy web.endpoint.dial
ziti edge delete service-policy web.endpoint.bind
echo Removing service config
ziti edge delete config web.endpoint.hostv1
echo Removing identity
ziti edge delete identity curlz
echo Removing service
ziti edge delete service web.endpointNOTE: If you followed Part 2 of this example, refer to teardown in the simple-server example README