forgejo/routers/api/v1/activitypub/repository.go

171 lines
5.5 KiB
Go
Raw Normal View History

// Copyright 2023 The forgejo Authors. All rights reserved.
2023-10-20 15:16:04 +02:00
// SPDX-License-Identifier: MIT
package activitypub
import (
"fmt"
2023-11-29 15:34:02 +01:00
"io"
2023-10-20 15:16:04 +02:00
"net/http"
"strings"
2023-10-20 15:16:04 +02:00
"code.gitea.io/gitea/models/activitypub"
2023-11-28 13:03:45 +01:00
api "code.gitea.io/gitea/modules/activitypub"
2023-10-20 15:16:04 +02:00
"code.gitea.io/gitea/modules/context"
2023-11-06 18:29:48 +01:00
"code.gitea.io/gitea/modules/forgefed"
"code.gitea.io/gitea/modules/log"
"code.gitea.io/gitea/modules/setting"
2023-11-10 14:26:13 +01:00
"code.gitea.io/gitea/modules/web"
ap "github.com/go-ap/activitypub"
//f3 "lab.forgefriends.org/friendlyforgeformat/gof3"
2023-10-20 15:16:04 +02:00
)
// Repository function returns the Repository actor for a repo
func Repository(ctx *context.APIContext) {
// swagger:operation GET /activitypub/repository-id/{repository-id} activitypub activitypubRepository
// ---
// summary: Returns the Repository actor for a repo
// produces:
// - application/json
// parameters:
// - name: repository-id
// in: path
// description: repository ID of the repo
// type: integer
// required: true
// responses:
// "200":
// "$ref": "#/responses/ActivityPub"
2023-11-15 12:10:31 +01:00
link := fmt.Sprintf("%s/api/v1/activitypub/repository-id/%d", strings.TrimSuffix(setting.AppURL, "/"), ctx.Repo.Repository.ID)
2023-11-06 18:29:48 +01:00
repo := forgefed.RepositoryNew(ap.IRI(link))
2023-11-06 18:29:48 +01:00
repo.Name = ap.NaturalLanguageValuesNew()
err := repo.Name.Set("en", ap.Content(ctx.Repo.Repository.Name))
if err != nil {
2023-11-06 18:29:48 +01:00
ctx.ServerError("Set Name", err)
return
}
2023-11-06 18:29:48 +01:00
response(ctx, repo)
2023-10-20 15:16:04 +02:00
}
// PersonInbox function handles the incoming data for a repository inbox
func RepositoryInbox(ctx *context.APIContext) {
// swagger:operation POST /activitypub/repository-id/{repository-id}/inbox activitypub activitypubRepository
// ---
// summary: Send to the inbox
// produces:
// - application/json
// parameters:
// - name: repository-id
// in: path
// description: repository ID of the repo
// type: integer
// required: true
2023-11-08 08:56:22 +01:00
// - name: body
// in: body
// schema:
// "$ref": "#/definitions/Star"
2023-10-20 15:16:04 +02:00
// responses:
// "204":
// "$ref": "#/responses/empty"
2023-11-06 08:49:58 +01:00
log.Info("RepositoryInbox: repo %v, %v", ctx.Repo.Repository.OwnerName, ctx.Repo.Repository.Name)
2023-11-10 14:26:13 +01:00
opt := web.GetForm(ctx).(*forgefed.Star)
2023-11-10 14:51:33 +01:00
log.Info("RepositoryInbox: Activity.Source %v", opt.Source)
2023-11-15 08:59:55 +01:00
log.Info("RepositoryInbox: Activity.Actor %v", opt.Actor)
2023-11-03 17:45:53 +01:00
2023-11-15 14:27:47 +01:00
// assume actor is: "actor": "https://codeberg.org/api/v1/activitypub/user-id/12345" - NB: This might be actually the ID? Maybe check vocabulary.
2023-11-15 09:23:03 +01:00
// parse actor
2023-11-29 13:26:35 +01:00
actor, err := activitypub.ParseActorIDFromStarActivity(opt)
// Is the actor IRI well formed?
if err != nil {
panic(err)
}
// Is the ActorData Struct valid?
2023-11-24 11:40:12 +01:00
actor.PanicIfInvalid()
2023-11-15 12:29:17 +01:00
log.Info("RepositoryInbox: Actor parsed. %v", actor)
2023-11-28 13:03:45 +01:00
/*
Make http client, this should make a get request on given url
We then need to parse the answer and put it into a person-struct
fill the person struct using some kind of unmarshall function given in
activitypub package/actor.go
*/
// make http client
2023-11-29 15:33:22 +01:00
host := opt.To.GetID().String()
client, err := api.NewClient(ctx, ctx.Doer, host) // ToDo: This is hacky, we need a hostname from somewhere
2023-11-28 13:03:45 +01:00
if err != nil {
panic(err)
}
2023-11-15 09:23:03 +01:00
// get_person_by_rest
2023-11-29 15:45:04 +01:00
bytes := []byte{0} // no body needed for getting user actor
target := opt.Actor.GetID().String() // target is the person actor that originally performed the star activity
response, err := client.Get(bytes, target)
2023-11-29 15:34:02 +01:00
if err != nil {
panic(err)
}
defer response.Body.Close()
body, err := io.ReadAll(response.Body)
if err != nil {
panic(err)
}
2023-11-29 15:45:04 +01:00
// parse response
person := ap.Person{}
err = person.UnmarshalJSON(body)
2023-11-29 15:34:02 +01:00
if err != nil {
panic(err)
}
2023-11-28 13:03:45 +01:00
2023-11-28 15:17:34 +01:00
log.Info("target: %v", target)
2023-11-28 13:03:45 +01:00
log.Info("http client. %v", client)
2023-11-28 15:17:34 +01:00
log.Info("response: %v\n error: ", response, err)
2023-11-29 15:34:02 +01:00
log.Info("Person is: %v", person)
2023-11-30 16:10:26 +01:00
log.Info("Person Name is: %v", person.PreferredUsername)
log.Info("Person URL is: %v", person.URL)
2023-11-17 17:20:36 +01:00
2023-11-15 09:23:03 +01:00
// create_user_from_person (if not alreaydy present)
2023-11-30 16:10:26 +01:00
/*
ToDo:
This might be a forgefed specification question?
How do we identify users from other places? Do we get the information needed to actually create a user?
E.g. email adress seems not to be part of the person actor (and may be considered sensitive info by some)
cmd/admin_user_create.go seems to require an EMail adress for user creation.
We might just create a user with a random email adress and a random password.
But what if that user wants to create an account at our instance with the same user name?
Or might it just be easier to change the data structure of the star and
save identifying info of a remote user there? That would make the star structure quite bloaty though.
It would also implicate that every other feature to be federated might need their own struct to be changed.
Or create a federated user struct?
That way, we could save the user info apart from any federated feature but tie it to that.
On a new registration we could check whether that user has already been seen as federated user and maybe ask if they want to connect these information.
Features to be federated in the future might benefit from that
The database of federated features will have to be updated with the new user values then.
The "if not already present" part might be easy:
Check the user database for given user id.
This could happen with something like: user_model.SearchUsers() as seen in routers/api/v1/user.go
SearchUsers is defined in models/user/search.go
And depending on implementation check if the person already exists in federated user db.
*/
2023-11-15 09:23:03 +01:00
// wait 15 sec.
2023-11-10 14:10:23 +01:00
2023-10-20 15:16:04 +02:00
ctx.Status(http.StatusNoContent)
2023-11-10 14:26:13 +01:00
2023-10-20 15:16:04 +02:00
}