On Thu, Feb 10, 2011 at 2:24 PM, Matt Amos <[email protected]> wrote:
> i might be missing the point here, but are you suggesting that OSM > would be an openID provider, consumer or both? I'm suggesting that instead of taking on a technology, we take on a set of requirements, or needs, and address them. And from there I'm saying that OpenID itself is a side issue. >> The second issue is OpenID support in general. >> >> MHO on the issue is that while it might seem that OpenID support is >> great and widely useful, I think there are a number of implementation >> issues and concerns which are really hard to overcome. >> >> For example, how does one handle OpenID with an API? This has been >> discussed in other contexts, and unfortunately there's no good single >> answer. > > my understanding is that openID would be usable on the website to > generate an OAuth token, which would then be used to access the API. > this seems like a good enough solution to me, but i could be missing > something. That sounds like it makes non-web based editors hard to develop. - Serge _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
