Skip to content

Commit 8550e06

Browse files
committed
chore: cleanup
1 parent fc2bc57 commit 8550e06

File tree

2 files changed

+15
-5
lines changed

2 files changed

+15
-5
lines changed

pocs/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,9 @@ want to share the endpoint to allow others to evaluate it by making GraphQL requ
1414

1515
The most simple (but somewhat risky) approach is to share the account's apikey (`stepzen whoami --apikey`).
1616

17-
The disadvantage with this is the admin key grants access to all endpoints within an account.
18-
Thus if you are working on different PoCs, by providing access to one you provide access to all
19-
which could leak information between different departments or clients.
17+
> [!WARNING]
18+
> The admin key grants access to all endpoints within an account. Thus if you are working on different PoCs, by providing access to one you provide access to all
19+
> which could leak information between different departments or clients.
2020
2121
### Obfuscated endpoints
2222

pocs/obfuscated-endpoint-url/README.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@ One simple mechanism to share an IBM API Connect Essentials (StepZen) endpoint t
44
to make the [endpoint open](../../protection/makeAllPublic/config.yaml) but
55
deploy the schema with an obfuscated name.
66

7+
## Deploying
8+
79
For example, deploy this schema using a randomly generated name (Linux/MacOS):
810

911
```
@@ -24,16 +26,22 @@ This endpoint URL can now be handed out to allow others to evaluate the endpoint
2426
> [!WARNING]
2527
> Anyone with the URL has access to the endpoint, so this is security through obscurity.
2628
27-
Using analytics the account owner can see activity with this specific endpoint,
29+
## Analytics
30+
31+
Using the analytics dashboard the account owner can see activity with this specific endpoint,
2832
so be handing out individual endpoints the account owner can track who has evaluated the endpoint.
2933

34+
## Single-use & deleting
35+
3036
Thus one can extend thise concept to a "single-use" endpoint, for example creating an endpoint
3137
for a demo and then delete it when no longer required.
3238

3339
```
3440
stepzen delete --non-interactive pocs/FzOYquoOMuQzvQqsLSUfVuvQwfVwuOEhGOkGGpLDnuIzeJZCHQAfHbFMCCIQdmBe
3541
```
3642

43+
## Tracking
44+
3745
By maintaining such endpoints in single folder, such as `pocs` or `single-use` you can use `stepzen list` to
3846
see which endpoints are still active.
3947

@@ -44,7 +52,9 @@ see which endpoints are still active.
4452
pocs/FzOYquoOMuQzvQqsLSUfVuvQwfVwuOEhGOkGGpLDnuIzeJZCHQAfHbFMCCIQdmBe Sep 8, 2024, 12:46 PM Sep 8, 2024, 12:59 PM
4553
```
4654

47-
It is recommended to define a schema description so that this GraphQL introspection request can
55+
## Description
56+
57+
It is recommended to define a [schema description](./index.graphql#L1-L6) so that this GraphQL introspection request can
4858
used to see the purpose of the obfuscated endpoint.
4959

5060
```

0 commit comments

Comments
 (0)