On 08/05/2013 03:30 PM, Alberto Mardegan wrote:
You can have many methods, but only one will be used:
<!-- The two lines above select the actual method/mechanism to be used -->
...and more methods...
As you can see, you can have many groups defined, but you also need to
tell which one will be used (or you can omit that information in the
.service file, if you store it directly in the accounts DB).
Aah, now I get it, makes sense.
Gsignond plugin is using "oauth" for method and "oauth2" or
mechanism. I didn't keep the original names for method and mechanisms
for these reasons:
- "oauth2" as a method name is confusing because the plugin also
- the combined mechanisms list is "web_server", "user_agent",
"PLAINTEXT" and "HMAC-SHA1". The first two are flow names from early
drafts of OAuth2 (they're no longer used in the final standard or in
google's documentation, and the final standard also specifies additional
flows), the latter two are signature methods from OAuth1.
I thought I'd better replace this with something simple, and have
version-specific flow parameters separately (GrantType and ResponseType
for Oauth2, and SignatureMethod for OAuth1).
I don't think it would be too hard. We just have to discuss any
changes on the mailing list, before implementing them.
You can find the documentation for the glib plugin here, so you can see
what else has changed: