You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note the server name in the `url=https://c5789aa0.ngrok.io` parameter (`https://c5789aa0.ngrok.io`) - this is the external url for your tails server. Make sure you use the `https` url!
130
131
132
+
If you see an "authentication failed" error in the logs like this:
133
+
```bash
134
+
ngrok-tails-server-1 | ERROR: authentication failed: Usage of ngrok requires a verified account and authtoken.
135
+
ngrok-tails-server-1 | ERROR:
136
+
ngrok-tails-server-1 | ERROR: Sign up for an account: https://dashboard.ngrok.com/signup
137
+
ngrok-tails-server-1 | ERROR: Install your authtoken: https://dashboard.ngrok.com/get-started/your-authtoken
138
+
```
139
+
then you'll need to follow the links to set up a ngrok account and get an authentication token.
140
+
When you have the authtoken, hit CTRL-C to exit from the logs and run the following commands,
141
+
replacing `<YOUR AUTHTOKEN>` with the authtoken from ngrok.
142
+
```bash
143
+
./manage logs # run above
144
+
^C
145
+
./manage stop
146
+
cat >>ngrok.yml
147
+
authtoken: <YOUR AUTHTOKEN>
148
+
^D
149
+
./manage start
150
+
./manage logs
151
+
```
152
+
131
153
#### Running in Play with Docker?
132
154
133
155
Run the same steps on _PWD_ as you would run locally (see above). Open a new shell (click on "ADD NEW INSTANCE") to run the tails server.
134
156
135
157
Note that with _Play with Docker_ it can be challenging to capture the information you need from the log file as it scrolls by, you can try leaving off the `--events` option when you run the Faber agent to reduce the quantity of information logged to the screen.
136
158
159
+
Also note that _PWD_ enviroments are insecure. If you enter a ngrok authtoken into a _PWD_ session, you should invalidate (reset) the authtoken as soon as you are done using the environment.
See the Connectionless Proof Request section below for a more complete ngrok configuration that also supports the revocation option.
250
+
221
251
## Issue a Credential
222
252
223
253
We will use the Faber console to issue a credential. This could be done using the Swagger API as we have done in the connection process. We'll leave that as an exercise to the user.
@@ -321,6 +351,28 @@ Then in the faber demo, select option `2a` - Faber will display a QR code which
321
351
322
352
Behind the scenes, the Faber controller delivers the proof request information (linked from the url encoded in the QR code) directly to your mobile agent, without establishing and agent-to-agent connection first. If you are interested in the underlying mechanics, you can review the `faber.py` code in the repository.
323
353
354
+
If you want to use a connectionless proof request with docker running locally, you need to set up ngrok to forward both the agent port (8020) and the webhooks port (8022). If you have a free ngrok account, you need to run a single ngrok agent that forwards all of the necessary ports. Here is an ngrok configuration file that works for this purpose:
355
+
```yaml
356
+
version: "3"
357
+
agent:
358
+
authtoken: <YOUR AUTHTOKEN>
359
+
tunnels:
360
+
acapy-agent:
361
+
proto: http
362
+
addr: 8020
363
+
acapy-webhooks:
364
+
proto: http
365
+
addr: 8022
366
+
tails-server:
367
+
addr: 6543
368
+
inspect: false
369
+
proto: http
370
+
```
371
+
When using this approach, leave your ngrok authtoken out of the tails-server ngrok.yml file to prevent the tails-server from starting its own ngrok agent. This trick avoids the following error from ngrok:
372
+
```bash
373
+
ERROR: authentication failed: Your account is limited to 1 simultaneous ngrok agent sessions.
374
+
```
375
+
324
376
## Conclusion
325
377
326
378
That’s the Faber-Mobile Alice demo. Feel free to play with the Swagger API and experiment further and figure out what an instance of a controller has to do to make things work.
0 commit comments