This project is read-only.

Extensibility of Confirmation of account email

Jan 3, 2014 at 1:49 AM
Edited Jan 3, 2014 at 2:12 AM
This confirmation of email feature is nice and more than welcome.

Now I am wondering if there are any plans to support extensibility for confirmation token of accounts registration data properties to support following scenarios:

Confirm mobile phone registered in Account extension

Generating token (simpler) for mobile phone confirmation (requires site integration) sent by one of the 3rd party SMS provider or Skype.

Generate token (simpler) with expiry time and action to taken when expired or confirmed

Some EU countries require consumer address registered in database to be validated in periodically and cleanse. This is to ensure that any database contains consumer address belongs to corresponding registered owner. The standard way is to send letter in certain periods and ask consumer to confirm the address by use of the letter confirmation code. This type confirmation code have longer expiry than email or mobile phone.

In essence, the above requirements could be simply satisfy by flexible token generation where generated token is persisted for particular action, such as email registration, email change, mobile phone change. These persisted token-action(s) can be used to confirm, they may expire in certain periods, or removed/revoked.
Jan 29, 2014 at 10:44 PM
@alexanderQX: In the beta release of Identity package, users can register phone numbers and confirm them. For the generic token provider, the current implementation is changed to have a generic user token provider. You can extend that behavior to your requirement.