@evan @julian @naturzukunft can keycloak parse a non-standard document to discover client metadata? No.

There were very specific reasons why myself and @aaronpk chose to make Client ID Metadata Documents the way we did: because we reused existing parts of the OAuth specification ecosystem.

Your proposal discards all that prior art in favour of making everything an AP actor.

@thisismissem @julian @naturzukunft it does what's necessary to enable the authorization code flow.

I think there's plenty of room for two tracks -- developers who want the complexity of discovery and registration can go your route, when you write it up.

Developers who just want to get the job done can use the simple and functional AP-centric mechanism in the OAuth FEP.

@julian @naturzukunft @thisismissem i don't think there's any assumption that way.

The one thing that the OAuth FEP assumes is that there's a way for the authorization server to validate the client ID and redirect URI by fetching the client ID.

I have not looked closely enough at keycloak to see if there's a way to build a plugin or to have configurable executable code to do that.

This seems like someone who really wants to use that configuration could take a few minutes to confirm.

@julian @naturzukunft @thisismissem i don't think there's any assumption that way.

The one thing that the OAuth FEP assumes is that there's a way for the authorization server to validate the client ID and redirect URI by fetching the client ID.

I have not looked closely enough at keycloak to see if there's a way to build a plugin or to have configurable executable code to do that.

This seems like someone who really wants to use that configuration could take a few minutes to confirm.

@evan @julian @naturzukunft OAuth isn't AP-centric, and never will be, that's probably your first error. Most OAuth clients will never need to be AP Actors.

Discovery isn't "complex", it's literally a HTTP request to a well known endpoint for a JSON document.

You can't do OAuth whilst ignoring all the OAuth standards.

@evan @julian @thisismissem
"I have not looked closely enough at keycloak to see if there's a way to build a plugin or to have configurable executable code to do that."

I don't plan to adapt a standard OAuth2 server to support ActivityPub. I think that if that's necessary, something is fundamentally wrong.

@naturzukunft @julian @thisismissem that's fine; you should do whatever it is you want.

@naturzukunft @julian @thisismissem oh, are you going to use Keycloak's built in user database, or are you going to use an adapter to fetch user data from your own database?

@naturzukunft @julian @thisismissem oh, are you going to use Keycloak's built in user database, or are you going to use an adapter to fetch user data from your own database?

@evan @julian @thisismissem which user data to do what ?

@naturzukunft @julian @thisismissem oh, sorry. By default, KeyCloak stores all the user data (name, avatar, description, so on) in its own internal PostgreSQL database, and you get an API to ask about and manage users.

The alternative is to add a custom UserStorageProvider class to access your own user storage and map your data to KeyCloak's schema. Applications that already have a user database often do this.

@naturzukunft @julian @thisismissem oh, are you going to use Keycloak's built in user database, or are you going to use an adapter to fetch user data from your own database?

@evan @naturzukunft @julian in the wild it's very uncommon to replace Keycloak's user database with something else; most commonly user migrations are performed, having been involved in several such projects.

@evan @julian @thisismissem There is a mapping in the resource server between PreferredUsername and an actor. This is a hack; I had to extend it because Mastodon uses the username as a unique identifier. Without Mastodon support, it would be a mapping between IssuerUserId and Actor. The data for the mapping comes from the JWT token.

But that's beside the point.

@evan @julian @thisismissem There is a mapping in the resource server between PreferredUsername and an actor. This is a hack; I had to extend it because Mastodon uses the username as a unique identifier. Without Mastodon support, it would be a mapping between IssuerUserId and Actor. The data for the mapping comes from the JWT token.

But that's beside the point.

@naturzukunft @julian @thisismissem I think your point was that any configuration that requires adding plugins or adapters for KeyCloak is a bad architecture, and you're committed to using KC entirely off-the-shelf.

@evan @naturzukunft @julian as Client ID Metadata Documents move through the standards process, I would assume keycloak will adopt them and Client ID Prefixes.

@evan @naturzukunft @julian as Client ID Metadata Documents move through the standards process, I would assume keycloak will adopt them and Client ID Prefixes.

@evan @naturzukunft @julian but keycloak being able to understand wtf a json-ld document of type Service or Application is? Incredibly unlikely, especially when the contents within isn't even remotely aligned with the IANA registry for Dynamic Client Registration Metadata values.