docs: Resolves broken policy and client definitions (#55)

Closes #53
ory · Mar 1, 2018 · 4676f40 · 4676f40
1 parent 1bbac52
commit 4676f40
Showing 1 changed file with 10 additions and 9 deletions.
diff --git a/docs/1-Quickstart/2-EXECUTION.md b/docs/1-Quickstart/2-EXECUTION.md
@@ -22,7 +22,7 @@ create two files:
 {
   "id": "oathkeeper-client",
   "client_secret": "something-secure",
-  "scope": "hydra.warden",
+  "scope": "hydra.warden hydra.keys.* hydra.introspect",
   "grant_types": ["client_credentials"],
   "response_types": ["token"]
 }
@@ -31,19 +31,20 @@ create two files:
 **policy.json**
 ```json
 {
-  "id": "oathkeeper-policy",
-  "subjects": [
-    "oathkeeper-client"
-  ],
+  "subjects": ["oathkeeper-client"],
   "effect": "allow",
   "resources": [
-    "rn:hydra:warden:allowed",
-    "rn:hydra:warden:token:allowed",
     "rn:hydra:keys:oathkeeper:id-token<.*>",
+    "rn:hydra:warden:<.*>",
+    "rn:hydra:oauth2:tokens"
   ],
   "actions": [
     "decide",
-    "get"
+    "get",
+    "create",
+    "introspect",
+    "update",
+    "delete"
   ]
 }
 ```
@@ -52,7 +53,7 @@ and import them using ORY Hydra's CLI:
 
 ```
 $ hydra clients import client.json
-$ hydra policies create -f policy.json
+$ hydra policies import policy.json
 ```
 
 Now we are all set to boot up ORY Oathkeeper. Because we are using the in-memory database backend, we have to use