Conversation

Notices

1. Embed this notice
   naturzukunft (naturzukunft@mastodon.social)'s status on Sunday, 07-Jan-2024 06:04:01 JST naturzukunft

   • Evan Prodromou

   puh, did a lot of work regarding blank nodes in #rdfpub. hope to be able to test @evan ap again tomorrow. time will be short again from monday. the money for rdf-pub has to come from somewhere ;-)
   #activitypub

   • clacke likes this.
   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Sunday, 07-Jan-2024 06:04:00 JST Evan Prodromou

     in reply to

     @naturzukunft 🙏🏽 can't wait to see it!

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Sunday, 14-Jan-2024 23:11:43 JST Evan Prodromou

     in reply to

     @naturzukunft https://codeberg.org/fediverse/fep/src/branch/main/fep/d8c2/fep-d8c2.md

   • Embed this notice
     naturzukunft (naturzukunft@mastodon.social)'s status on Sunday, 14-Jan-2024 23:11:44 JST naturzukunft

     in reply to

     • Evan Prodromou

     @evan happens when i execute
     ap login max@dev.rdf-pub.org

   • Embed this notice
     naturzukunft (naturzukunft@mastodon.social)'s status on Sunday, 14-Jan-2024 23:11:45 JST naturzukunft

     in reply to

     • Evan Prodromou

     @evan took a little longer after all ;-)
     what oauth2 client do you use ? is it dynamic client registration? but then i would expect another error.
     my keycloak says:

   • Embed this notice
     naturzukunft (naturzukunft@mastodon.social)'s status on Monday, 15-Jan-2024 03:42:37 JST naturzukunft

     in reply to

     • Evan Prodromou

     @evan i saw now, that the client_id is also in the token request and wrapped that too.

     now i've:

     oauthlib.oauth2.rfc6749.errors.CustomOAuth2Error: (RESTEASY003650: No resource method found for GET, return 405 with Allow header)

     "RESTEASY003650" sounds like a keycloak error.

     i'm afraid i won't get any further without your support.

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Monday, 15-Jan-2024 03:42:37 JST Evan Prodromou

     in reply to

     @naturzukunft I feel like we're close. Let's take a step back. The FEP describes a way to provide a client_id to the OAuth 2.0 server that is itself an ActivityPub object. You can see the one for `ap` here: https://evanp.github.io/ap/client.jsonld Can keycloak extract the `redirectURI` property from that object?

   • Embed this notice
     naturzukunft (naturzukunft@mastodon.social)'s status on Monday, 15-Jan-2024 03:42:38 JST naturzukunft

     in reply to

     • Evan Prodromou

     @evan ok, i'm now able to forward your request to keycloak and the login dialog is shown. but after login ap says:

     127.0.0.1 - - [...] "GET /callback?state=xxxxx&session_state=xxxxxxx HTTP/1.1" 200 -
     ...

     File "/usr/lib/python3/dist-packages/oauthlib/oauth2/rfc6749/parameters.py", line 451, in validate_token_parameters
     raise MissingTokenError(description="Missing access token parameter.")
     oauthlib.oauth2.rfc6749.errors.MissingTokenError: (missing_token) Missing access token parameter.

   • Embed this notice
     naturzukunft (naturzukunft@mastodon.social)'s status on Monday, 15-Jan-2024 04:18:56 JST naturzukunft

     in reply to

     • Evan Prodromou

     @evan my server is playing man in the middle! so the answer is somehow yes and no ;-)

     See this code: https://gitlab.com/linkedopenactors/rdf-pub/-/blob/feature/blank_nodes/rdf-pub-adapter-driving/src/main/java/org/linkedopenactors/rdfpub/adapter/driving/Oauth2Test.java?ref_type=heads#L53

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Monday, 15-Jan-2024 04:18:56 JST Evan Prodromou

     in reply to

     @naturzukunft OK, I don't know enough about Keycloak to know why this isn't working. But you're passing along the client's redirect URI; a lot of OAuth servers require that the redirect URI match a pre-registered value. So, that might be one source of the error.

   • Embed this notice
     naturzukunft (naturzukunft@mastodon.social)'s status on Monday, 15-Jan-2024 05:56:36 JST naturzukunft

     in reply to

     • Evan Prodromou

     @evan

     The description before the json says: "https://followrec.example/client".
     The id in the json is "https:/followrec.example/apps/myapp".
     Shouldn't they be identical?

     https://codeberg.org/fediverse/fep/src/branch/main/fep/d8c2/fep-d8c2.md#follower-recommender

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Monday, 15-Jan-2024 05:56:36 JST Evan Prodromou

     in reply to

     @naturzukunft yes, good catch!