#GWGIt pulls all rels now, because I might code support for redirect_uri for whitelisting
#GWGaaronpk: I just realized I have to manage multiple types of tokens. The Bearer Token, the Authorization Code, and now the State are all being generated the same way. I think I'd better reorganize that.
[grantcodes], jeremycherfas, jeremych- and jeremycherfas_ joined the channel; jeremycherfas left the channel
#GWGOkay. Auth code and Access token moved over to more featured way of management. State next
#GWGaaronpk: I've done a whole boatload of stuff in IndieAuth. I may ask you to have a look when I'm done. It should make it easier to manage the code, I hope.
#GWGI thought I did. People don't always read the readme
#aaronpkGWG: from what I can tell, the plugin now always makes an HTTP request to itself when the token endpoint is verifying the authorization code. I thought you had code in there that looked that up in the database instead
#aaronpkoh huh, looks like that was the case in the previous version of the plugin too. so I guess that didn't change in this PR
#GWGI did, pfefferle removed it. I may restore it in future
#aaronpkit makes no sense to have the plugin make an http request to itself. that adds so many potential points of failure to what otherwise would be a very straightforward check
#aaronpkI thought class-indieauth-authenticate.php was the file where this plugin consumes other indieauth servers for web sign-in. is that correct?
#GWGIt still is, but the new websignin class started splitting off the login interface. Why?
#GWGAuthenticate probably should eventually be renamed authorize
#aaronpkthere's a bunch of stuff in class-indieauth-authenticate.php about scopes and setting headers, which isn't used at all if you're consuming an existing IndieAuth identity
#GWGIt is a completed attempt, but I think there is always more to do
#aaronpkof course there is always more to do. but it's very confusing when you use language like "trying to" because it is not clear whether I am looking at something intended to actually work
#aaronpkhm local access token verification seems to have been taken out as well
[pfefferle] joined the channel
#[pfefferle][aaronpk] I removed the local stuff, because the code tries to verify the authentication code with it’s local endpoint instead of the endpoint of the other party… we discussed that a lot
#aaronpk[pfefferle]: this is for the web sign-in flow tho right?
#aaronpkso it could say "you need to install this other plugin now" kind of thing
#GWG"We have split the sign-on portion into a separate plugin. IndieAuth will only contain the IndieAuth endpoints and authorization code. Please install the web sign-in plugin if you want to sign into your WordPress site with an external IndieAuth endpoint."
#aaronpkGWG: so I just tested it, and something in class-indieauth-authenticate.php is still required for web sign-in to work
#GWGaaronpk: I'll get it all out. I should have tested that
#aaronpkwhich plugin adds rel=me links to your home page? is that the IndieWeb plugin?
#GWGThere are manual ways, of course, but that is the one that takes them from your user profile.
#aaronpkquestion for GWG and pfefferle: hypothetically, in this new standalone web sign-in plugin, would you like to use indielogin.com as a fallback authentication option if the user is signing in with a site that doesn't support IndieAuth?
#GWGaaronpk: I would think so. But is it ready for that?
#aaronpknot yet, which is why I said hypothetically
#aaronpkokay, I installed the IndieAuth plugin for web-sign-in on a test site on a real server so I'll be able to continue to test pfefferle's use case there
#GWGI meant as part of the user to url problem, but I'm not worried about it
#aaronpkI was able to log in as aaronparecki.com there with the current published version of the plugin
#aaronpkI logged in as https://tiny.xyz.dev/blog/ into the micropub app, and it issued a token for that URL, so it should be able to verify that token too
#aaronpkespecially since this site is in single-user mode
#aaronpkwith local token verification this wouldn't be a problem
#aaronpksince the user_id is stored along with the token record
#aaronpkso there's no URL matching or lookup that has to happen
#aaronpkplease do fix surfacing those errors, but how do you feel about ripping out the remote token stuff and replacing it with local lookup right now? now that web sign-in is isolated I don't think there's a use case that requires using a remote indieauth server now