Actor profile has internal domains for publicKey id and owner.

From https://github.com/xwiki-contrib/application-activitypub/issues/37

After digging further, I discovered why Mastodon was not finding my XWiki user. In my attempt to workaround the non-standard webfinger endpoint, I added the webfinger data to another server. People sometimes do this to get redirects from personal domain names to a shared AP server. Today I learned that Mastodon will do a webfinger double-check using a webfinger server at the domain of the resolved actor. Since I was using Cloudflare Tunnels without Nginx and an XWiki webfinger redirect, the second webfinger query to my XWiki container failed.

Unfortunately, after I configured an Nginx reverse proxy, I had a couple of new problems. First, it appears that the URL scheme described in the docs isn't accurate. After trying many variations, I found that http://serverUrl/webfinger/?resource=\{actorId}@{domain} does work (no /xwiki/ in the URL). The second problem was that {{

}} only worked with the internal LAN domain and not the public reverse-proxied domain. Using the public domain returned "No user found for the given domain".

At this point, I think I'm stuck unless someone has some suggestions (or I have time to refresh my Java skills and create a PR). I'm going to create a few separate issues to make these easier to track.