Like the thought of owning my own online identity via a URL endpoint.. This could mean centralized personal control of you data down the line. https://aaronparecki.com/2018/07/07/7/oauth-for-the-open-web
WeChat ID
aaronpk_tv
-
In two weeks, I'm hosting a series of OAuth/OpenID Connect workshops in Chicago, Dallas, and San Francisco with @okta! They're free to attend and there's food/drinks afterwards! Sign up here ➡ http://regionalevents.okta.com/developerworkshoproadshow -
-
-
Good: the screws I ordered from China arrived 2 days before the 14-30 day delivery window.
Bad: they are 2mm too short for what I need! -
I absolutely ❤️ the idea of the #IndieWeb. Take control of your own content! watch @adactio explain it: https://vimeo.com/265121482 https://indieweb.org
-
I could see extending the limitation of the loopback address to also include the private IP ranges. I assume in that case it is extremely unlikely that the server will have an https certificate, so that's another reason to keep the limitation on the private IP ranges rather than allowing arbitrary IP addresses.
One of the benefits of the client ID being a publicly accessible web page is that the authorization server can fetch the application name and icon from that page.
In the case of using a private IP address, the authorization server won't be able to fetch any information about the client, so the prompt will show just the IP.
The other option is to use
https://www.home-assistant.io/as the client ID, allowing just the redirect URL to be a private IP. This breaks the rule of the client ID and redirect URL hostnames matching, so servers may show a warning like the below, but at least the application info is visible.
-
-
Michael Bishop
https://miklb.com
•
Jul 8
My greatest lifehack has probably been removing the laptop charger from near the couch.
And here i was thinking about installing one there permanently -
This evening I’ve been trying to build a minimal http://glitch.com app which supports IndieAuth login. After some head scratching I see it’s a tweaked oauth2 flow, I think.
Goals:
- remixable (Glitch shines there)
- transparent
- well tested -
I think that's all the brain power I've got for today. Feels good to have another IndieAuth server implementation in the wild now tho!
-
I just implemented an IndieAuth server for Aperture, which sounds crazy but it's actually pretty cool. Now you can log in to apps like https://indiepaper.io and they can post content directly into a private channel!
If you have an Aperture account, try logging in to Quill using https://aperture.p3k.io as your URL. Here's a little demo of it in action! -
