It is possible to have many "method/mechanism" entries in
section of .provider and .service files. So, if your oauth2 plugin
needs different parameters than ours, you can simply call it
differently (like, "goauth2").
If it is possible, I don't see how: ag_account_service_get_auth_data() returns a
single instance of AuthData, and AuthData has a single method for fetching the method and
a single method for fetching the mechanism. Accordingly, the xml format doesn't seem
to allow such setup either:
<?xml version="1.0" encoding="UTF-8" ?>
<_description>Includes Gmail, Google Docs, Google+, YouTube and
Can you explain?
If we cannot eliminate the differences between UOA and Tizen,
recommend that EDS treats them as different entities, and therefore
installs different .service files depending on the parameters passed to
the ./configure script. Then, ag_account_service_get_auth_data() will
return the correct values.
I think Patrick would like to have fully run-time detection of available SSO-specific auth
settings and SSO backends. We can of course try to eliminate the differences in oauth
plugins' API, but then we also need to commit to maintaining the compatibility.