Original Summary

I keep coming back to the same problem when working with APIs: each service needs authentication, but maintaining separate login and token handling across a stack creates duplicated work and inconsistent behaviour. I’m building P’adentro , a self-hosted service that APIs can delegate authentication to. The current design gives each API a tenant with scoped permissions and issues short-lived signed access tokens that the API can verify locally. I’m gathering people for a private beta. The site has a waitlist rather than immediate access: https://padentro.dev/ I’d value blunt feedback from anyone who has managed auth across multiple APIs: Would you consider a separate self-hosted service for this? What would you need to see before trusting it with authentication? Which integration or operational concern would stop you from trying it? I’m the person building it, and I’ll answer questions here.   submitted by   /u/manelcecs [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/28 05:00:58