Issue 244 in accounts-sso: [gsignond] password plugin is too restrictive

[accoun...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 244 by tintou.n...@gmail.com: [gsignond] password plugin is too
restrictive
https://code.google.com/p/accounts-sso/issues/detail?id=244

The password plugin doesn't process anything.
there are a ot of properties that could be useful with it, here are some:
#define SIGNONUI_KEY_FORGOT_PASSWORD "ForgotPassword"
#define SIGNONUI_KEY_FORGOT_PASSWORD_URL "ForgotPasswordUrl"
#define SIGNONUI_KEY_QUERY_PASSWORD "QueryPassword"
#define SIGNONUI_KEY_QUERY_USERNAME "QueryUserName"

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[accoun...@googlecode.com]

Updates:
Status: Invalid

Comment #1 on issue 244 by alex.kan...@gmail.com: [gsignond] password

plugin is too restrictive
https://code.google.com/p/accounts-sso/issues/detail?id=244

Yeah, gsso has lots of unused key definitions for plugins; that is not a
bug.

If there is something that original sso has, but gsso doesn't, or something
that you think gsso should have, let us know, but be *specific*.

[accoun...@googlecode.com]

Comment #2 on issue 244 by jussi.la...@linux.intel.com: [gsignond] password

plugin is too restrictive
https://code.google.com/p/accounts-sso/issues/detail?id=244

Those properties are used between plugin, gsignond and signonui.
QueryPassword and QueryUserName are already supported by the password
plugin. These are not properties for the SessionData. You can use
#define SIGNON_SESSION_DATA_UI_POLICY "UiPolicy"
to achieve both QueryPassword and QueryUserName using
SIGNON_POLICY_REQUEST_PASSWORD value depending if username is stored in the
database or not.

We could at some point extend the session data to pass data for the
ForgotPasswordUrl through.