dex/examples/README.md

# Running Examples

The quickest way to start experimenting with dex is to run a single dex-worker locally, with an in-process database, and then interact with it using the example programs in this directory.

## Build Everything and Start dex-worker

First, build the example webapp client and example CLI client.

```console
./build
```

Now copy the example configurations into place to get dex configured.
You can customize these later but the defaults should work fine.

```console
cp static/fixtures/clients.json.sample static/fixtures/clients.json
cp static/fixtures/connectors.json.sample static/fixtures/connectors.json
cp static/fixtures/users.json.sample static/fixtures/users.json
cp static/fixtures/emailer.json.sample static/fixtures/emailer.json
```

With `dex-worker` configuration in place we can start dex in local mode.

```console
./bin/dex-worker --no-db &
```

## Example Webapp Client

Build and run the example app webserver by pointing the discovery URL to local Dex, and
supplying the client information from `./static/fixtures/clients.json` into the flags.

```console
./bin/example-app \
	--client-id=example-app \
	--client-secret=eZXhhbXBsZS1jbGktc2VjcmV0 \
	--discovery=http://127.0.0.1:5556
```

Visit [http://localhost:5555](http://localhost:5555) in your browser and click "login" link.
Next click "Login with Email" and enter the sample credentials from `static/fixtures/connectors.json`:

* email: `elroy77@example.com`
* password: `bones`

The example app will dump out details of the JWT issued by Dex which means that authentication was successful and the application has authenticated you as a valid user.
You can play with adding additional users in connectors.json and users.json.

## Example CLI Client

The example CLI will start, connect to the Dex instance to gather discovery information, listen on `localhost:8000`, and then acquire a client credentials JWT and print it out.

```console
./bin/example-cli \
	--client-id example-cli \
	--client-secret ZXhhbXBsZS1jbGktc2VjcmV0 \
	--discovery=http://127.0.0.1:5556
```
examples: improve docs in README Make the docs feel more like a tutorial and add some more context. 2015-11-09 07:47:55 +05:30			`# Running Examples`
*: move original project to dex 2015-08-18 05:57:27 +05:30
examples: improve docs in README Make the docs feel more like a tutorial and add some more context. 2015-11-09 07:47:55 +05:30			`The quickest way to start experimenting with dex is to run a single dex-worker locally, with an in-process database, and then interact with it using the example programs in this directory.`
*: move original project to dex 2015-08-18 05:57:27 +05:30
			`## Build Everything and Start dex-worker`

examples: improve docs in README Make the docs feel more like a tutorial and add some more context. 2015-11-09 07:47:55 +05:30			`First, build the example webapp client and example CLI client.`

Documentation: update dev-guide.md and examples/README.md - Be more explicit with exact instructions to startup - Change some of the commands that were using local directory with "./" when the executable was in a lower directory. These commands (like "./bin/dex-worker") did not work on ZSH or Bash, so I removed the leading "./" - Add some syntax highlighting markdown to code sections 2015-11-07 01:44:44 +05:30			```console
examples: improve docs in README Make the docs feel more like a tutorial and add some more context. 2015-11-09 07:47:55 +05:30			`./build`
			```

			`Now copy the example configurations into place to get dex configured.`
			`You can customize these later but the defaults should work fine.`

Documentation: update dev-guide.md and examples/README.md - Be more explicit with exact instructions to startup - Change some of the commands that were using local directory with "./" when the executable was in a lower directory. These commands (like "./bin/dex-worker") did not work on ZSH or Bash, so I removed the leading "./" - Add some syntax highlighting markdown to code sections 2015-11-07 01:44:44 +05:30			```console
examples: add sample for clients Adds consistency to existing samples for users, connectors, etc., as well as protects users from accidental changes to files under Git, which is why there are samples after all. 2016-05-19 06:48:20 +05:30			`cp static/fixtures/clients.json.sample static/fixtures/clients.json`
examples: improve docs in README Make the docs feel more like a tutorial and add some more context. 2015-11-09 07:47:55 +05:30			`cp static/fixtures/connectors.json.sample static/fixtures/connectors.json`
			`cp static/fixtures/users.json.sample static/fixtures/users.json`
			`cp static/fixtures/emailer.json.sample static/fixtures/emailer.json`
			```

			With `dex-worker` configuration in place we can start dex in local mode.

Documentation: update dev-guide.md and examples/README.md - Be more explicit with exact instructions to startup - Change some of the commands that were using local directory with "./" when the executable was in a lower directory. These commands (like "./bin/dex-worker") did not work on ZSH or Bash, so I removed the leading "./" - Add some syntax highlighting markdown to code sections 2015-11-07 01:44:44 +05:30			```console
examples: improve docs in README Make the docs feel more like a tutorial and add some more context. 2015-11-09 07:47:55 +05:30			`./bin/dex-worker --no-db &`
			```

			`## Example Webapp Client`

examples: add sample for clients Adds consistency to existing samples for users, connectors, etc., as well as protects users from accidental changes to files under Git, which is why there are samples after all. 2016-05-19 06:48:20 +05:30			`Build and run the example app webserver by pointing the discovery URL to local Dex, and`
*: move original project to dex 2015-08-18 05:57:27 +05:30			supplying the client information from `./static/fixtures/clients.json` into the flags.
examples: improve docs in README Make the docs feel more like a tutorial and add some more context. 2015-11-09 07:47:55 +05:30
Documentation: update dev-guide.md and examples/README.md - Be more explicit with exact instructions to startup - Change some of the commands that were using local directory with "./" when the executable was in a lower directory. These commands (like "./bin/dex-worker") did not work on ZSH or Bash, so I removed the leading "./" - Add some syntax highlighting markdown to code sections 2015-11-07 01:44:44 +05:30			```console
examples: improve docs in README Make the docs feel more like a tutorial and add some more context. 2015-11-09 07:47:55 +05:30			`./bin/example-app \`
			`--client-id=example-app \`
*: update examples to hold valid client secrets for no-db mode 2016-08-12 01:23:48 +05:30			`--client-secret=eZXhhbXBsZS1jbGktc2VjcmV0 \`
examples: improve docs in README Make the docs feel more like a tutorial and add some more context. 2015-11-09 07:47:55 +05:30			`--discovery=http://127.0.0.1:5556`
			```

			`Visit [http://localhost:5555](http://localhost:5555) in your browser and click "login" link.`
Documentation: update dev-guide.md and examples/README.md - Be more explicit with exact instructions to startup - Change some of the commands that were using local directory with "./" when the executable was in a lower directory. These commands (like "./bin/dex-worker") did not work on ZSH or Bash, so I removed the leading "./" - Add some syntax highlighting markdown to code sections 2015-11-07 01:44:44 +05:30			Next click "Login with Email" and enter the sample credentials from `static/fixtures/connectors.json`:
examples: improve docs in README Make the docs feel more like a tutorial and add some more context. 2015-11-09 07:47:55 +05:30
Documentation: update dev-guide.md and examples/README.md - Be more explicit with exact instructions to startup - Change some of the commands that were using local directory with "./" when the executable was in a lower directory. These commands (like "./bin/dex-worker") did not work on ZSH or Bash, so I removed the leading "./" - Add some syntax highlighting markdown to code sections 2015-11-07 01:44:44 +05:30			* email: `elroy77@example.com`
			* password: `bones`
examples: improve docs in README Make the docs feel more like a tutorial and add some more context. 2015-11-09 07:47:55 +05:30
			`The example app will dump out details of the JWT issued by Dex which means that authentication was successful and the application has authenticated you as a valid user.`
			`You can play with adding additional users in connectors.json and users.json.`

			`## Example CLI Client`

			The example CLI will start, connect to the Dex instance to gather discovery information, listen on `localhost:8000`, and then acquire a client credentials JWT and print it out.

Documentation: update dev-guide.md and examples/README.md - Be more explicit with exact instructions to startup - Change some of the commands that were using local directory with "./" when the executable was in a lower directory. These commands (like "./bin/dex-worker") did not work on ZSH or Bash, so I removed the leading "./" - Add some syntax highlighting markdown to code sections 2015-11-07 01:44:44 +05:30			```console
examples: improve docs in README Make the docs feel more like a tutorial and add some more context. 2015-11-09 07:47:55 +05:30			`./bin/example-cli \`
Update README.md Fix command line for example-cli 2016-04-21 00:23:36 +05:30			`--client-id example-cli \`
*: update examples to hold valid client secrets for no-db mode 2016-08-12 01:23:48 +05:30			`--client-secret ZXhhbXBsZS1jbGktc2VjcmV0 \`
examples: improve docs in README Make the docs feel more like a tutorial and add some more context. 2015-11-09 07:47:55 +05:30			`--discovery=http://127.0.0.1:5556`
			```