Issues with linked actors

Bug
1

We just merged a commit that adds support for Discourse-to-Discourse linked actors on the ActivityPub plugin, however, on testing in two different instances, I am seeing issues. Filing them all here @angus so that they’re grouped together.

Discourse-to-Discourse verification: in a personal Discourse instance, I can’t add a Discourse Linked Actor from meta.discourse.org, initially I got a “failed to verify” client error, and then a timeout.

Screenshots:

CleanShot 2024-12-19 at 15.51.09@2x
CleanShot 2024-12-19 at 15.51.09@2x1384×572 10.4 KB

CleanShot 2024-12-19 at 15.50.30@2x
CleanShot 2024-12-19 at 15.50.30@2x1636×472 18.2 KB

Same error when trying to link my personal instance account from meta.

Discourse-to-Mastodon verification: on the personal instance, this worked Ok! Here on meta though, I can’t seem to get past the verify step for mastodon.social, I get this error: An error occurred: The access token is invalid Failed to verify client.

1 Like
2

Just a note that I’ve started working on this and will have an update / PR soon.

1 Like
3

@pmusaraj Just as an initial measure I’ve made a PR that adds settings for the rate limiting of user api key clients (which will make this hard to test this).

Could you also just check that discourse-activity-pub:read scope is added to the allow user_api key client scopes site setting. It should be automatically, but worth checking.

1 Like