-
Notifications
You must be signed in to change notification settings - Fork 515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Webhook URL configuration parameter looses its api key #1419
Comments
I'll look into this |
OK there's an issue going on but I don't think its related to web hooks. (As an aside there is a potential to erase the webhook api key, but it's related to the admin config endpoint, not message re-tries. See PR: #1420 So ... I don't think this is what's causing the BPA issue.) When I added some debugging and ran a test (connect BPA1 and BPA2 via a connection invitation) it looks like the authentication is failing on the acapy-to-acapy messages, not the webhook messages. See the following log -
|
It looks like (in the logs above) the agents are advertising their endpoints as |
... when I fixed the aca-py agent endpoints, everything seems to work fine:
|
I do not think this is what is causing the issue. I have the first aca-py connected to a BPA in my IDE like I can produce this behaviour by simply shutting down the BPA in the IDE. As soon as there is a connection between two agents there is a ping job running, so another agent is constantly sending messages that aca-py tries to send via the webhook. This fails now with a connection error:
Here the header is still set, but as soon as the BPA is started again the header is gone. So after restart the same logging statement:
Without scrolling, before
After:
|
@etschelp thanks for the info. Can you upload the aca-py log for this test (with |
See the following log: |
This is the issue:
See my comment above re PR # 1420 |
Thanks a lot for figuring that out. This makes a lot of sense, as the BPA loads the admin config directly after startup hence erasing the api key. |
Fixed with version > 0.7.2-rc0 |
I have aca-py deployed with the api key set in the webhook url, for example
--webhook-url http://localhost:8080/something#mykey
. This causes aca-py to sent an x-api-key header when calling the webhook. Since 0.7.0 this still works but as soon as the controller becomes unavailable for a short time e.g. restart, or is not available when aca-py starts up the header is not set any more. To be more specific the first call on the webhook after the restart still has the header, the second hasn't.I'm not an aca-py expert and maybe this is the wrong place but manager.py overwrites the endpoint variable with the result of the splitting action. If now for some reason the handler gets recreated it would continue without the api key.
The text was updated successfully, but these errors were encountered: