Hi Indunil,
We need to also enforce captcha on the self signup Rest API (following the
same pattern implemented for other Rest APIs), because the self signup API
only has application level authentication and users who can access the
application (by default "*authenticationendpoint"*) are able
Hi,
Thanks all for your valuable feedbacks, it will be helpful to improve this
in future.
In the design discussion (Refer [1]), it's concluded that to implement a
generic OSGI service for resending confirmation code in account recovery
scenarios and self registration and to consider other
Hi,
On Tue, Dec 5, 2017 at 9:03 AM, Johann Nallathamby wrote:
> Hi Indunil/Isura,
>
> I have a general comment on this. Are we not planning to support this in
> the UI at least in the public release? Because planning for backend only
> IMO is not a good idea from previous
HI,
On Tue, Dec 5, 2017 at 8:15 AM, Isura Karunaratne wrote:
> Hi Indunil,
>
>
>
> On Mon, Dec 4, 2017 at 8:24 PM, Indunil Upeksha Rathnayake <
> indu...@wso2.com> wrote:
>
>> Hi,
>>
>> With IS 5.3.0, we have currently provided a Rest API for resending
>> confirmation code
Hi Indunil/Isura,
I have a general comment on this. Are we not planning to support this in
the UI at least in the public release? Because planning for backend only
IMO is not a good idea from previous experience because it will remain at
the same state for years. Don't want to go back there. And
On Mon, Dec 4, 2017 at 6:54 AM, Indunil Upeksha Rathnayake wrote:
> Hi,
>
> With IS 5.3.0, we have currently provided a Rest API for resending
> confirmation code (Refer [1]), which supports only for self signup feature.
> So that, we are planning to provide a more generic
Hi,
With IS 5.3.0, we have currently provided a Rest API for resending
confirmation code (Refer [1]), which supports only for self signup feature.
So that, we are planning to provide a more generic REST API and a OSGi
service, for resending confirmation code for any scenario.
Following are the