opened
apendleton
username_0
It looks like Hecate preserves the OSM distinction between publicly accessible read-only content and auth-required read-write access. I wonder if this makes sense going forward. If a usecase for this service is potentially store internal-use/private data, reads would also need to be protected. It seems like, freed from the constraints of OSM's code, you'd either want to secure everything at the network level, or everything with username/password, but I'm not sure why you'd additional levels of auth/protection for some parts of the service than for others. Maybe it's just a constraint imposed by a desire to still interoperate with JOSM?
Auth story?
issue
created
ingalls
username_1
@username_0 yup, as you mention above - the auth story has to duplicate that of OSM to enjoy the benefits of using JOSM/iD.
comment
created
ingalls
username_1
Hecate auth is now fully customizable per the `Custom Authentication` section of the readme
comment
closed
ingalls
username_1
issue