Re: [Architecture] Supporting Email or Mobile as the Preferred Communication Channel for Users

[Ruwan Abeykoon]

Hi Sominda,
We are discussing in architecture list, and we should discuss on 5.10.0 or
any new releases. We should not discuss about how to add features on old
releases.
We should not use registry for any new features, as registry has been known
to cause problems.

Cheers,
Ruwan A

On Thu, Nov 28, 2019 at 4:46 PM Sominda Gamage  wrote:

> Hi Ruwan,
>
> We are giving this feature in IS 5.7.0 as a WUM and for 5.7.0, new config
> store API is not ready. Since the email templates are managed from the
> registry, we decided to manage SMS notification templates from there as
> well.
> Since we are giving this to a previous IS version, I feel this has the
> lowest overhead during a migration.
>
> Regards,
> Sominda.
>
>
> On Thu, Nov 28, 2019 at 3:08 PM Ruwan Abeykoon  wrote:
>
>> Hi Sominda,
>> Better not use registry any more for any new functionality.
>> Can we use new config store ?
>>
>> Cheers,
>> Ruwan A
>>
>> On Thu, Nov 28, 2019 at 3:05 PM Sominda Gamage  wrote:
>>
>>> Hi all,
>>>
>>> According to the implementation, the SMS templates are stored inside the
>>> *email-admin-config.xml* file. Even though this works perfectly, the
>>> procedure is incorrect. Therefore I have decided to change the storing
>>> location of the SMS notification templates.
>>>
>>> *Proposed solution*
>>> - Store the SMS templates in a different registry folder.
>>> - Add and notification templates from the registry.
>>> - Introduce a new API to EmailTemplateManager to resolve the templates
>>> from the template type.
>>>
>>> Thanks and regards,
>>> Sominda.
>>>
>>> On Wed, Nov 27, 2019 at 11:06 AM Sominda Gamage 
>>> wrote:
>>>
 Hi all,

 I have written several blogs explaining the feature and configurations.
 Please find the links below. Currently, this feature does not have a
 tutorial. I will make a new tutorial for this feature and update the mail
 thread.

 [1] - User Self Registration and Account Confirmation via Mobile and
 Email Channels in WSO2 Identity Server
 
 [2] - Requests and Responses of User Self Registration REST APIs in
 WSO2 Identity Server
 
 [3] - Configuring WSO2 Identity Server to Support Multiple
 notification channels
 

 Thanks,
 Sominda.

 On Wed, Nov 27, 2019 at 7:41 AM Sominda Gamage 
 wrote:

> Hi all,
>
>
> WUM update for User Self-Registration via Email and SMS is released
> for WSO2 IS 5.7.0 and WSO2 IS 5.7.0 KM. The update number is 5734. The
> configuration details are provided in doc [1] and [2].
>
>
> Document [1] contains a detailed description of the functionality of
> the API with sample API requests and responses. Also, Doc [1] contains 
> more
> information on notification channel selecting criteria. Document [2]
> contains the configurations that are needed to configure self-registration
> to support multiple channels.
>
>
> Improvements by the feature.
>
>- The feature is provided only via the user self-registration APIs
>- A new service has been introduced to determine the preferred
>channel of the user.
>- A new identity claim is introduced to track the preferred
>notification channel of the user.
>- The responses of User-Self registration API has been introduced.
>   - By default this configuration is disabled.
>- The functionality of the Account Confirmation API has been
>improved.
>   - For more information refer to the extended account
>   confirmation api
>   
> 
>   .
>
>
>
> [1] -
> https://docs.wso2.com/display/IS570/Extending+User+Self+Registration+and+Account+Confirmation
>
> [2] -
> https://docs.wso2.com/display/IS570/Configuring+a+User+Preferred+Notification+Channel
>
>
> Thanks & Regards,
>
> Sominda.
>
> On Wed, Nov 27, 2019 at 7:40 AM Sominda Gamage 
> wrote:
>
>> Hi all,
>>
>> I have implemented APIs to support self registration via mobile
>> (SMS) or EMAIL as account confirmation channels. According to the
>> implementation, I have defined two notification channels and each channel
>> has several claims bound to it.
>>
>>- Channel Name (EMAIL or SMS)
>>- Channel Value Claim - Claim to store the value of the claims
>>(Eg: http

Re: [Architecture] Supporting Email or Mobile as the Preferred Communication Channel for Users

[Ruwan Abeykoon]

Hi Sominda,
Better not use registry any more for any new functionality.
Can we use new config store ?

Cheers,
Ruwan A

On Thu, Nov 28, 2019 at 3:05 PM Sominda Gamage  wrote:

> Hi all,
>
> According to the implementation, the SMS templates are stored inside the
> *email-admin-config.xml* file. Even though this works perfectly, the
> procedure is incorrect. Therefore I have decided to change the storing
> location of the SMS notification templates.
>
> *Proposed solution*
> - Store the SMS templates in a different registry folder.
> - Add and notification templates from the registry.
> - Introduce a new API to EmailTemplateManager to resolve the templates
> from the template type.
>
> Thanks and regards,
> Sominda.
>
> On Wed, Nov 27, 2019 at 11:06 AM Sominda Gamage  wrote:
>
>> Hi all,
>>
>> I have written several blogs explaining the feature and configurations.
>> Please find the links below. Currently, this feature does not have a
>> tutorial. I will make a new tutorial for this feature and update the mail
>> thread.
>>
>> [1] - User Self Registration and Account Confirmation via Mobile and
>> Email Channels in WSO2 Identity Server
>> 
>> [2] - Requests and Responses of User Self Registration REST APIs in WSO2
>> Identity Server
>> 
>> [3] - Configuring WSO2 Identity Server to Support Multiple notification
>> channels
>> 
>>
>> Thanks,
>> Sominda.
>>
>> On Wed, Nov 27, 2019 at 7:41 AM Sominda Gamage  wrote:
>>
>>> Hi all,
>>>
>>>
>>> WUM update for User Self-Registration via Email and SMS is released for
>>> WSO2 IS 5.7.0 and WSO2 IS 5.7.0 KM. The update number is 5734. The
>>> configuration details are provided in doc [1] and [2].
>>>
>>>
>>> Document [1] contains a detailed description of the functionality of the
>>> API with sample API requests and responses. Also, Doc [1] contains more
>>> information on notification channel selecting criteria. Document [2]
>>> contains the configurations that are needed to configure self-registration
>>> to support multiple channels.
>>>
>>>
>>> Improvements by the feature.
>>>
>>>- The feature is provided only via the user self-registration APIs
>>>- A new service has been introduced to determine the preferred
>>>channel of the user.
>>>- A new identity claim is introduced to track the preferred
>>>notification channel of the user.
>>>- The responses of User-Self registration API has been introduced.
>>>   - By default this configuration is disabled.
>>>- The functionality of the Account Confirmation API has been
>>>improved.
>>>   - For more information refer to the extended account confirmation
>>>   api
>>>   
>>> 
>>>   .
>>>
>>>
>>>
>>> [1] -
>>> https://docs.wso2.com/display/IS570/Extending+User+Self+Registration+and+Account+Confirmation
>>>
>>> [2] -
>>> https://docs.wso2.com/display/IS570/Configuring+a+User+Preferred+Notification+Channel
>>>
>>>
>>> Thanks & Regards,
>>>
>>> Sominda.
>>>
>>> On Wed, Nov 27, 2019 at 7:40 AM Sominda Gamage  wrote:
>>>
 Hi all,

 I have implemented APIs to support self registration via mobile (SMS)
 or EMAIL as account confirmation channels. According to the
 implementation, I have defined two notification channels and each channel
 has several claims bound to it.

- Channel Name (EMAIL or SMS)
- Channel Value Claim - Claim to store the value of the claims (Eg:
http://wso2.org/claims/mobile)
- Channel Verified Claim -  A claim to store the verified status of
the channel (Eg: http://wso2.org/claims/phoneVerified)

 Following are the claims associated with each channel

- *Email*
   - Channel Name: EMAIL
   - Value Claim: http://wso2.org/claims/emailaddress
   - Verified Claim: http://wso2.org/claims/emailVerified
- *Mobile*
   - Channel Name: SMS
   - Value Claim: http://wso2.org/claims/mobile
   - Verified Claim: http://wso2.org/claims/phoneVerified

 The following properties were added to identity.xml.


 1. Configurations in *identity.xml* within the ** tags to
 resolve the notification channels.


 **

 *EMAIL*
 **

 *true *


 *   *

 **


 2. Configurations in *identity.xml* within the **
 tags.




 *true*


 *True*


 **