Johnathan Garrett
unread,Aug 22, 2013, 10:39:18 AM8/22/13Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to geo...@opengeo.org
Hey everyone,
We need to think of how we want to handle authentication of http remotes in the long term. Right now we have set up our GeoServer to require authentication to access the exposed GeoGit repositories. There is currently no support in GeoGit for providing authentication information for requests to the web API, so we have set up a hard coded default Authenticator in HTTPRemoteRepo on a separate branch that allows us to communicate with the remote.
What should the long term authentication solution be, and how should it be used to work with auto-synchronization implementations?
Thanks,
- JD