Re: [Dev] GSOC 2016 - Project 21 : Review Proposal

[Asantha Thilina]

Hi Tharindu,

As you advice i updated my blog[1] with all my works i have done so far ,
looking for your feedback

[1]. http://asanthamax.blogspot.com/

Thanks,
Asantha

On Fri, May 6, 2016 at 11:21 AM, Asantha Thilina <asanthathil...@gmail.com>
wrote:

> Hi Tharindu,
>
> i have done some coding in my user store ,does mongodb contain a
> parameterized query mechanism such as prepared statements in sql?
> i search through mongodb documentation and i didn't find any related idea
> therefore i create my own class to do that job and i tested it with sample
> data for all 4 CRUDS and it worked. my logic will be as follows,
> first it will read the query as json input,
> then as same as in prepared statement when function calling has to pass
> what are the parameters as example i can define the template query as
> follows
> {'UM_USER_NAME': '?'}
> then has to convert this query to DBObject and parse to find function with
> parameters and respective collection name as follows
> find("UM_USER",object,"test");
> so that then in find function i mapping the corresponding parameter to
> suitable query position but the problem in how would i  sanitize the user
> input parameters to avoid security threats as in prepared statements? do i
> have to write regular expressions or is their any other way of doing? is
> sql injections kind of thing possible with mongodb if so how would i escape
> it?
> i would be thankful if you can review my code and give me a feedback
> whether my logic is correct and also is there are a way to write schema in
> mongodb like in sql?
>
> all my works up to this is added to my repository in here [1]
>
> [1]. https://github.com/asanthamax/mongodbuserstore
>
> Thanks,
> Asantha
>
> On Thu, May 5, 2016 at 11:24 AM, Asantha Thilina <asanthathil...@gmail.com
> > wrote:
>
>> ------ Forwarded message ------
>> From: Asantha Thilina <asanthathil...@gmail.com>
>> Date: Mon, May 2, 2016 at 12:46 AM
>> Subject: Re: [Dev] GSOC 2016 - Project 21 : Review Proposal
>> To: Tharindu Edirisinghe <tharin...@wso2.com>, dev@wso2.org
>>
>>
>> Hi Tharindu,
>>
>> as you adviced i started creating corresponding mongodb database
>> structure for IS user store i done the user store database script and share
>> it in here [1] and identity script still writing  before further progress
>> on identity script i would be very thankful if i can get your comment about
>> my user store script whether it correct or need to improve while i mapping
>> mysql script to mongodb i faced on following issue
>> MongoDB is not supporting to multikey hashed indexes according to their
>> documentation in here [2] therefore i create one hash index per document
>> which are need hash indexes
>> for mapping foreign keys i used the manual way than db refs or embeded
>> documents to avoid data repition for that i refer their documentation in
>> here [3]
>> For storage engine i used the default engine called wired tiger according
>> to their documentation in here [4]
>> waiting for your feedback about my works,
>> [1].
>> https://github.com/asanthamax/mongodbuserstore/blob/master/identity_server.js
>> [2]. https://docs.mongodb.org/v3.0/tutorial/create-a-hashed-index/
>> [3]. https://docs.mongodb.org/manual/reference/database-references/
>> [4]. https://docs.mongodb.org/manual/core/wiredtiger/
>>
>> Thanks,
>> Asantha
>>
>> On Sat, Apr 30, 2016 at 4:02 AM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> thanks for the guidance sure i'll do that way and update you as i
>>> progress
>>>
>>> Thanks,
>>> Asantha
>>>
>>> On Fri, Apr 29, 2016 at 10:00 PM, Tharindu Edirisinghe <
>>> tharin...@wso2.com> wrote:
>>>
>>>> Hi Asantha,
>>>>
>>>> Great work ! Yes, you will have to manually create the database with
>>>> the tables. Then once you create the userstore in Identity Server and point
>>>> to the particular database, it should work properly.
>>>>
>>>> Then what you can do here is converting the relational db schema to
>>>> collections in mongodb. You can refer the IS_5.1.0_HOME/dbscripts/ location
>>>> where all the database scripts are stored. You need to look at only 2 sql
>>>> files for the moment. They are the IS_5.1.0_HOME/dbscripts/mysql.sql and
>>>> IS_5.1.0_HOME/dbscripts/identity/mysql.sql . Referring these two files, you
>>>> can write 2 sql files for mongodb.
>>>>
>>>>

Re: [Dev] GSOC 2016 - Project 21 : Review Proposal

[Asantha Thilina]

Hi Tharindu,

i have done some coding in my user store ,does mongodb contain a
parameterized query mechanism such as prepared statements in sql?
i search through mongodb documentation and i didn't find any related idea
therefore i create my own class to do that job and i tested it with sample
data for all 4 CRUDS and it worked. my logic will be as follows,
first it will read the query as json input,
then as same as in prepared statement when function calling has to pass
what are the parameters as example i can define the template query as
follows
{'UM_USER_NAME': '?'}
then has to convert this query to DBObject and parse to find function with
parameters and respective collection name as follows
find("UM_USER",object,"test");
so that then in find function i mapping the corresponding parameter to
suitable query position but the problem in how would i  sanitize the user
input parameters to avoid security threats as in prepared statements? do i
have to write regular expressions or is their any other way of doing? is
sql injections kind of thing possible with mongodb if so how would i escape
it?
i would be thankful if you can review my code and give me a feedback
whether my logic is correct and also is there are a way to write schema in
mongodb like in sql?

all my works up to this is added to my repository in here [1]

[1]. https://github.com/asanthamax/mongodbuserstore

Thanks,
Asantha

On Thu, May 5, 2016 at 11:24 AM, Asantha Thilina <asanthathil...@gmail.com>
wrote:

> -- Forwarded message --
> From: Asantha Thilina <asanthathil...@gmail.com>
> Date: Mon, May 2, 2016 at 12:46 AM
> Subject: Re: [Dev] GSOC 2016 - Project 21 : Review Proposal
> To: Tharindu Edirisinghe <tharin...@wso2.com>, dev@wso2.org
>
>
> Hi Tharindu,
>
> as you adviced i started creating corresponding mongodb database structure
> for IS user store i done the user store database script and share it in
> here [1] and identity script still writing  before further progress on
> identity script i would be very thankful if i can get your comment about my
> user store script whether it correct or need to improve while i mapping
> mysql script to mongodb i faced on following issue
> MongoDB is not supporting to multikey hashed indexes according to their
> documentation in here [2] therefore i create one hash index per document
> which are need hash indexes
> for mapping foreign keys i used the manual way than db refs or embeded
> documents to avoid data repition for that i refer their documentation in
> here [3]
> For storage engine i used the default engine called wired tiger according
> to their documentation in here [4]
> waiting for your feedback about my works,
> [1].
> https://github.com/asanthamax/mongodbuserstore/blob/master/identity_server.js
> [2]. https://docs.mongodb.org/v3.0/tutorial/create-a-hashed-index/
> [3]. https://docs.mongodb.org/manual/reference/database-references/
> [4]. https://docs.mongodb.org/manual/core/wiredtiger/
>
> Thanks,
> Asantha
>
> On Sat, Apr 30, 2016 at 4:02 AM, Asantha Thilina <asanthathil...@gmail.com
> > wrote:
>
>> Hi Tharindu,
>>
>> thanks for the guidance sure i'll do that way and update you as i progress
>>
>> Thanks,
>> Asantha
>>
>> On Fri, Apr 29, 2016 at 10:00 PM, Tharindu Edirisinghe <
>> tharin...@wso2.com> wrote:
>>
>>> Hi Asantha,
>>>
>>> Great work ! Yes, you will have to manually create the database with the
>>> tables. Then once you create the userstore in Identity Server and point to
>>> the particular database, it should work properly.
>>>
>>> Then what you can do here is converting the relational db schema to
>>> collections in mongodb. You can refer the IS_5.1.0_HOME/dbscripts/ location
>>> where all the database scripts are stored. You need to look at only 2 sql
>>> files for the moment. They are the IS_5.1.0_HOME/dbscripts/mysql.sql and
>>> IS_5.1.0_HOME/dbscripts/identity/mysql.sql . Referring these two files, you
>>> can write 2 sql files for mongodb.
>>>
>>> Later we can do some modifications to automatically create the database
>>> (if the mongodb userstore is selected to be the PRIMARY userstore)
>>> referring the schema in above 2 files.
>>>
>>> Regards,
>>> TharinduE
>>>
>>> On Fri, Apr 29, 2016 at 10:22 PM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
>>>> Hi Tharindu,
>>>>
>>>> Thanks for the instructions As you described in mail i followed all the
>>>> steps and i  have been now able to see my new user store service is started
>>>> and shown in IS as

Re: [Dev] GSOC 2016 - Project 21 : Review Proposal

[Asantha Thilina]

Hi Tharindu,

i have done some coding in my new mongodb user store and i shared my code
here [1]  i will be developing it by referring JDBC user store in here[2]
,is their any wso2 coding conventions i should follow ?can you review my
code and give me a feedback is their any improvement to be done

[1] https://github.com/asanthamax/mongodbuserstore
[2]
https://svn.wso2.org/repos/wso2/branches/carbon/3.2.0/core/org.wso2.carbon.user.core/3.2.3/src/main/java/org/wso2/carbon/user/core/jdbc/JDBCUserStoreManager.java

Thanks,
Asantha

On Mon, May 2, 2016 at 12:46 AM, Asantha Thilina 
wrote:

> Hi Tharindu,
>
> as you adviced i started creating corresponding mongodb database structure
> for IS user store i done the user store database script and share it in
> here [1] and identity script still writing  before further progress on
> identity script i would be very thankful if i can get your comment about my
> user store script whether it correct or need to improve while i mapping
> mysql script to mongodb i faced on following issue
> MongoDB is not supporting to multikey hashed indexes according to their
> documentation in here [2] therefore i create one hash index per document
> which are need hash indexes
> for mapping foreign keys i used the manual way than db refs or embeded
> documents to avoid data repition for that i refer their documentation in
> here [3]
> For storage engine i used the default engine called wired tiger according
> to their documentation in here [4]
> waiting for your feedback about my works,
> [1].
> https://github.com/asanthamax/mongodbuserstore/blob/master/identity_server.js
> [2]. https://docs.mongodb.org/v3.0/tutorial/create-a-hashed-index/
> [3]. https://docs.mongodb.org/manual/reference/database-references/
> [4]. https://docs.mongodb.org/manual/core/wiredtiger/
>
> Thanks,
> Asantha
>
> On Sat, Apr 30, 2016 at 4:02 AM, Asantha Thilina  > wrote:
>
>> Hi Tharindu,
>>
>> thanks for the guidance sure i'll do that way and update you as i progress
>>
>> Thanks,
>> Asantha
>>
>> On Fri, Apr 29, 2016 at 10:00 PM, Tharindu Edirisinghe <
>> tharin...@wso2.com> wrote:
>>
>>> Hi Asantha,
>>>
>>> Great work ! Yes, you will have to manually create the database with the
>>> tables. Then once you create the userstore in Identity Server and point to
>>> the particular database, it should work properly.
>>>
>>> Then what you can do here is converting the relational db schema to
>>> collections in mongodb. You can refer the IS_5.1.0_HOME/dbscripts/ location
>>> where all the database scripts are stored. You need to look at only 2 sql
>>> files for the moment. They are the IS_5.1.0_HOME/dbscripts/mysql.sql and
>>> IS_5.1.0_HOME/dbscripts/identity/mysql.sql . Referring these two files, you
>>> can write 2 sql files for mongodb.
>>>
>>> Later we can do some modifications to automatically create the database
>>> (if the mongodb userstore is selected to be the PRIMARY userstore)
>>> referring the schema in above 2 files.
>>>
>>> Regards,
>>> TharinduE
>>>
>>> On Fri, Apr 29, 2016 at 10:22 PM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Tharindu,

 Thanks for the instructions As you described in mail i followed all the
 steps and i  have been now able to see my new user store service is started
 and shown in IS as you suggested i have changed the username and password
 fields to mandatory and updated code i shared in here [1] after adding new
 mongodb user store under new user store section in IS it gives the success
 message but nothing showing at the user store list in admin console here i
 attached screenshots of my IS console ,would i need to create database with
 all the necessary tables to add new user store?

 [1]. https://github.com/asanthamax/mongodbuserstore

 Thanks,
 Asantha

 On Thu, Apr 28, 2016 at 7:48 PM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi Tharindu,
>
> Thanks for the reply ,i will follow the instructions and update you
>
> Thanks,
> Asantha
>
> On Fri, Apr 29, 2016 at 8:10 AM, Tharindu Edirisinghe <
> tharin...@wso2.com> wrote:
>
>> Hi Asantha,
>>
>> Can you try out the following steps in a fresh (new) Identity Server
>> 5.1.0 pack.
>>
>> 1. Put the MongoDB JDBC driver in repository/components/lib directory.
>> 2. Build the mongodb userstore manager and copy the built jar file to
>> repository/components/dropins directory.
>> 3. Connect to the mongodb shell and create an admin user.
>>
>> *> use admin*
>> switched to db admin
>> *> db.createUser({user:"admin", pwd:"admin123", roles:[{role:"root",
>> db:"admin"}]})*
>> Successfully added user: {
>> "user" : "admin",
>> "roles" : [
>> {
>> "role" : "root",
>> "db" : "admin"
>> }
>> ]
>> }

Re: [Dev] GSOC 2016 - Project 21 : Review Proposal

[Asantha Thilina]

Hi Tharindu,

that's fine i'll be ok with that time

Thanks,
Asantha

On Tue, Apr 26, 2016 at 8:36 AM, Tharindu Edirisinghe 
wrote:

> Hi Asantha,
>
> How about 4.30 p.m today ?
>
> Regards,
> TharinduE
>
> On Mon, Apr 25, 2016 at 8:19 PM, Asantha Thilina  > wrote:
>
>> Hi Tharindu,
>>
>> thanks for the wishes and i am really interesting and looking forward to
>> continue on project,yeah sure we will  have a hangout and i would be
>> grateful if we can arrange the meeting on evening round about 3.00 P.M. or
>> any time later that ,is it ok
>>
>> Thanks,
>> Asantha
>>
>> On Mon, Apr 25, 2016 at 6:57 AM, Tharindu Edirisinghe > > wrote:
>>
>>> Hi Asantha,
>>>
>>> Congratulations on getting selected for GSOC 2016 ! Hope you are doing
>>> well. Shall we have a google hangout tomorrow 26/04/2016 to discuss how to
>>> proceed with the project ? What time would suit you ?
>>>
>>> Regards,
>>> TharinduE
>>>
>>> On Thu, Mar 24, 2016 at 9:18 AM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi all,

 Thanks a lot for your valuable comments and feedback i done all the
 changes as you suggested in feedback and submitted the final document to
 google ,modified google doc is in here[1]

 [1]
 https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing

 Thanks,
 Asantha

 On Wed, Mar 23, 2016 at 8:08 PM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi Tharindu,
>
> thanks for the comment, sure i  do the modifications as suggested,
>
> Thanks,
> Asantha
>
> On Wed, Mar 23, 2016 at 6:54 PM, Tharindu Edirisinghe <
> tharin...@wso2.com> wrote:
>
>> Hi Asantha,
>>
>> I've done some minor modifications to the doc. For the methods
>> exposed through the API, can you add them in a table to improve the
>> readability. (Chamila has suggested this already as a comment in the 
>> doc).
>> You can have some columns for Method Name, Return type, parameters,
>> description.
>>
>> Once you do this, submit it to google because the deadline is
>> tomorrow for proposal submission.
>>
>> Thanks,
>> TharinduE
>>
>> On Wed, Mar 23, 2016 at 9:08 PM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> I modified my project proposal[1] in google doc, as you suggested i
>>> added function list which i am going to exposed to apis after modified 
>>> the
>>> content  i shared the doc to summer of code.
>>> waiting for your feedback
>>> [1]
>>> https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing
>>>
>>> Thanks,
>>> Asantha
>>>
>>> On Tue, Mar 22, 2016 at 8:16 PM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Tharindu,

 thanks a lot for the feedbacks, sure i will modify the content of
 the proposal as suggested  and submit to google within today

 Thanks,
 Asantha


 On Wed, Mar 23, 2016 at 7:45 AM, Tharindu Edirisinghe <
 tharin...@wso2.com> wrote:

> Hi Asantha,
>
> I've added the latest proposal you've sent to google docs in [1].
> As Chamila suggested, can you list down the methods that you expose 
> in the
> API (public methods in the userstore manager) in the proposal so that 
> it is
> easy to understand the functionality of the userstore manager. Also 
> it is
> better to submit the proposal to google now and update later if any
> modification is needed.
>
> [1]
> https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing
>
> Thanks,
> TharinduE
>
> On Mon, Mar 21, 2016 at 9:58 PM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Chamila,
>>
>> Thanks a lot for the feedback, sure i will update my proposal as
>> you suggested
>>
>> Thanks,
>> Asantha
>>
>> On Mon, Mar 21, 2016 at 9:18 AM, Chamila Wijayarathna <
>> cham...@wso2.com> wrote:
>>
>>> Hi Asantha,
>>>
>>> Looks good, please talk with Tharindu also before submitting the
>>> proposal. Even you submit your proposal, you can improve it until 
>>> 25th.
>>>
>>> So if time permits, I would like to suggest you to add some
>>> details about what are the APIs and functions you are going to 
>>> expose after
>>> developing this new user store manager, if you have already decided 
>>> on
>>> them. Since you may have went through the codes of existing user 

Re: [Dev] GSOC 2016 - Project 21 : Review Proposal

[Tharindu Edirisinghe]

Hi Asantha,

How about 4.30 p.m today ?

Regards,
TharinduE

On Mon, Apr 25, 2016 at 8:19 PM, Asantha Thilina 
wrote:

> Hi Tharindu,
>
> thanks for the wishes and i am really interesting and looking forward to
> continue on project,yeah sure we will  have a hangout and i would be
> grateful if we can arrange the meeting on evening round about 3.00 P.M. or
> any time later that ,is it ok
>
> Thanks,
> Asantha
>
> On Mon, Apr 25, 2016 at 6:57 AM, Tharindu Edirisinghe 
> wrote:
>
>> Hi Asantha,
>>
>> Congratulations on getting selected for GSOC 2016 ! Hope you are doing
>> well. Shall we have a google hangout tomorrow 26/04/2016 to discuss how to
>> proceed with the project ? What time would suit you ?
>>
>> Regards,
>> TharinduE
>>
>> On Thu, Mar 24, 2016 at 9:18 AM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> Thanks a lot for your valuable comments and feedback i done all the
>>> changes as you suggested in feedback and submitted the final document to
>>> google ,modified google doc is in here[1]
>>>
>>> [1]
>>> https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing
>>>
>>> Thanks,
>>> Asantha
>>>
>>> On Wed, Mar 23, 2016 at 8:08 PM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Tharindu,

 thanks for the comment, sure i  do the modifications as suggested,

 Thanks,
 Asantha

 On Wed, Mar 23, 2016 at 6:54 PM, Tharindu Edirisinghe <
 tharin...@wso2.com> wrote:

> Hi Asantha,
>
> I've done some minor modifications to the doc. For the methods exposed
> through the API, can you add them in a table to improve the readability.
> (Chamila has suggested this already as a comment in the doc). You can have
> some columns for Method Name, Return type, parameters, description.
>
> Once you do this, submit it to google because the deadline is tomorrow
> for proposal submission.
>
> Thanks,
> TharinduE
>
> On Wed, Mar 23, 2016 at 9:08 PM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Tharindu,
>>
>> I modified my project proposal[1] in google doc, as you suggested i
>> added function list which i am going to exposed to apis after modified 
>> the
>> content  i shared the doc to summer of code.
>> waiting for your feedback
>> [1]
>> https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing
>>
>> Thanks,
>> Asantha
>>
>> On Tue, Mar 22, 2016 at 8:16 PM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> thanks a lot for the feedbacks, sure i will modify the content of
>>> the proposal as suggested  and submit to google within today
>>>
>>> Thanks,
>>> Asantha
>>>
>>>
>>> On Wed, Mar 23, 2016 at 7:45 AM, Tharindu Edirisinghe <
>>> tharin...@wso2.com> wrote:
>>>
 Hi Asantha,

 I've added the latest proposal you've sent to google docs in [1].
 As Chamila suggested, can you list down the methods that you expose in 
 the
 API (public methods in the userstore manager) in the proposal so that 
 it is
 easy to understand the functionality of the userstore manager. Also it 
 is
 better to submit the proposal to google now and update later if any
 modification is needed.

 [1]
 https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing

 Thanks,
 TharinduE

 On Mon, Mar 21, 2016 at 9:58 PM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi Chamila,
>
> Thanks a lot for the feedback, sure i will update my proposal as
> you suggested
>
> Thanks,
> Asantha
>
> On Mon, Mar 21, 2016 at 9:18 AM, Chamila Wijayarathna <
> cham...@wso2.com> wrote:
>
>> Hi Asantha,
>>
>> Looks good, please talk with Tharindu also before submitting the
>> proposal. Even you submit your proposal, you can improve it until 
>> 25th.
>>
>> So if time permits, I would like to suggest you to add some
>> details about what are the APIs and functions you are going to 
>> expose after
>> developing this new user store manager, if you have already decided 
>> on
>> them. Since you may have went through the codes of existing user 
>> store
>> managers, you may already have an idea about what are the functions 
>> you
>> need to exposed to outside. So if can add at least few functions you 
>> are
>> going to expose with some details, it would make your proposal more
>> attractive. Also I would 

Re: [Dev] GSOC 2016 - Project 21 : Review Proposal

[Asantha Thilina]

Hi Tharindu,

thanks for the wishes and i am really interesting and looking forward to
continue on project,yeah sure we will  have a hangout and i would be
grateful if we can arrange the meeting on evening round about 3.00 P.M. or
any time later that ,is it ok

Thanks,
Asantha

On Mon, Apr 25, 2016 at 6:57 AM, Tharindu Edirisinghe 
wrote:

> Hi Asantha,
>
> Congratulations on getting selected for GSOC 2016 ! Hope you are doing
> well. Shall we have a google hangout tomorrow 26/04/2016 to discuss how to
> proceed with the project ? What time would suit you ?
>
> Regards,
> TharinduE
>
> On Thu, Mar 24, 2016 at 9:18 AM, Asantha Thilina  > wrote:
>
>> Hi all,
>>
>> Thanks a lot for your valuable comments and feedback i done all the
>> changes as you suggested in feedback and submitted the final document to
>> google ,modified google doc is in here[1]
>>
>> [1]
>> https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing
>>
>> Thanks,
>> Asantha
>>
>> On Wed, Mar 23, 2016 at 8:08 PM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> thanks for the comment, sure i  do the modifications as suggested,
>>>
>>> Thanks,
>>> Asantha
>>>
>>> On Wed, Mar 23, 2016 at 6:54 PM, Tharindu Edirisinghe <
>>> tharin...@wso2.com> wrote:
>>>
 Hi Asantha,

 I've done some minor modifications to the doc. For the methods exposed
 through the API, can you add them in a table to improve the readability.
 (Chamila has suggested this already as a comment in the doc). You can have
 some columns for Method Name, Return type, parameters, description.

 Once you do this, submit it to google because the deadline is tomorrow
 for proposal submission.

 Thanks,
 TharinduE

 On Wed, Mar 23, 2016 at 9:08 PM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi Tharindu,
>
> I modified my project proposal[1] in google doc, as you suggested i
> added function list which i am going to exposed to apis after modified the
> content  i shared the doc to summer of code.
> waiting for your feedback
> [1]
> https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing
>
> Thanks,
> Asantha
>
> On Tue, Mar 22, 2016 at 8:16 PM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Tharindu,
>>
>> thanks a lot for the feedbacks, sure i will modify the content of the
>> proposal as suggested  and submit to google within today
>>
>> Thanks,
>> Asantha
>>
>>
>> On Wed, Mar 23, 2016 at 7:45 AM, Tharindu Edirisinghe <
>> tharin...@wso2.com> wrote:
>>
>>> Hi Asantha,
>>>
>>> I've added the latest proposal you've sent to google docs in [1]. As
>>> Chamila suggested, can you list down the methods that you expose in the 
>>> API
>>> (public methods in the userstore manager) in the proposal so that it is
>>> easy to understand the functionality of the userstore manager. Also it 
>>> is
>>> better to submit the proposal to google now and update later if any
>>> modification is needed.
>>>
>>> [1]
>>> https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing
>>>
>>> Thanks,
>>> TharinduE
>>>
>>> On Mon, Mar 21, 2016 at 9:58 PM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Chamila,

 Thanks a lot for the feedback, sure i will update my proposal as
 you suggested

 Thanks,
 Asantha

 On Mon, Mar 21, 2016 at 9:18 AM, Chamila Wijayarathna <
 cham...@wso2.com> wrote:

> Hi Asantha,
>
> Looks good, please talk with Tharindu also before submitting the
> proposal. Even you submit your proposal, you can improve it until 
> 25th.
>
> So if time permits, I would like to suggest you to add some
> details about what are the APIs and functions you are going to expose 
> after
> developing this new user store manager, if you have already decided on
> them. Since you may have went through the codes of existing user store
> managers, you may already have an idea about what are the functions 
> you
> need to exposed to outside. So if can add at least few functions you 
> are
> going to expose with some details, it would make your proposal more
> attractive. Also I would like to suggest you to add link of github 
> repo
> where you have started development. Also if you have written any blogs
> related to the project, mongoDB, etc. please mention them also in your
> proposal.
>
> Also I see some formatting issues and some dates has got repeated
> 

Re: [Dev] GSOC 2016 - Project 21 : Review Proposal

[Tharindu Edirisinghe]

Hi Asantha,

Congratulations on getting selected for GSOC 2016 ! Hope you are doing
well. Shall we have a google hangout tomorrow 26/04/2016 to discuss how to
proceed with the project ? What time would suit you ?

Regards,
TharinduE

On Thu, Mar 24, 2016 at 9:18 AM, Asantha Thilina 
wrote:

> Hi all,
>
> Thanks a lot for your valuable comments and feedback i done all the
> changes as you suggested in feedback and submitted the final document to
> google ,modified google doc is in here[1]
>
> [1]
> https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing
>
> Thanks,
> Asantha
>
> On Wed, Mar 23, 2016 at 8:08 PM, Asantha Thilina  > wrote:
>
>> Hi Tharindu,
>>
>> thanks for the comment, sure i  do the modifications as suggested,
>>
>> Thanks,
>> Asantha
>>
>> On Wed, Mar 23, 2016 at 6:54 PM, Tharindu Edirisinghe > > wrote:
>>
>>> Hi Asantha,
>>>
>>> I've done some minor modifications to the doc. For the methods exposed
>>> through the API, can you add them in a table to improve the readability.
>>> (Chamila has suggested this already as a comment in the doc). You can have
>>> some columns for Method Name, Return type, parameters, description.
>>>
>>> Once you do this, submit it to google because the deadline is tomorrow
>>> for proposal submission.
>>>
>>> Thanks,
>>> TharinduE
>>>
>>> On Wed, Mar 23, 2016 at 9:08 PM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Tharindu,

 I modified my project proposal[1] in google doc, as you suggested i
 added function list which i am going to exposed to apis after modified the
 content  i shared the doc to summer of code.
 waiting for your feedback
 [1]
 https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing

 Thanks,
 Asantha

 On Tue, Mar 22, 2016 at 8:16 PM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi Tharindu,
>
> thanks a lot for the feedbacks, sure i will modify the content of the
> proposal as suggested  and submit to google within today
>
> Thanks,
> Asantha
>
>
> On Wed, Mar 23, 2016 at 7:45 AM, Tharindu Edirisinghe <
> tharin...@wso2.com> wrote:
>
>> Hi Asantha,
>>
>> I've added the latest proposal you've sent to google docs in [1]. As
>> Chamila suggested, can you list down the methods that you expose in the 
>> API
>> (public methods in the userstore manager) in the proposal so that it is
>> easy to understand the functionality of the userstore manager. Also it is
>> better to submit the proposal to google now and update later if any
>> modification is needed.
>>
>> [1]
>> https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing
>>
>> Thanks,
>> TharinduE
>>
>> On Mon, Mar 21, 2016 at 9:58 PM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Chamila,
>>>
>>> Thanks a lot for the feedback, sure i will update my proposal as you
>>> suggested
>>>
>>> Thanks,
>>> Asantha
>>>
>>> On Mon, Mar 21, 2016 at 9:18 AM, Chamila Wijayarathna <
>>> cham...@wso2.com> wrote:
>>>
 Hi Asantha,

 Looks good, please talk with Tharindu also before submitting the
 proposal. Even you submit your proposal, you can improve it until 25th.

 So if time permits, I would like to suggest you to add some details
 about what are the APIs and functions you are going to expose after
 developing this new user store manager, if you have already decided on
 them. Since you may have went through the codes of existing user store
 managers, you may already have an idea about what are the functions you
 need to exposed to outside. So if can add at least few functions you 
 are
 going to expose with some details, it would make your proposal more
 attractive. Also I would like to suggest you to add link of github repo
 where you have started development. Also if you have written any blogs
 related to the project, mongoDB, etc. please mention them also in your
 proposal.

 Also I see some formatting issues and some dates has got repeated
 in your timeline, hope you will correct the when submitting proposal at
 GSoC site.

 Cheers!

 On Mon, Mar 21, 2016 at 9:18 PM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi Chamila,
>
> Thanks a lot for your valuable feedback as you suggested i
> corrected my project proposal and here i attached my finalize project
> proposal
>
> expecting your feedback
>
> Thanks,
> Asantha
>
> On Mon, 

Re: [Dev] GSOC 2016 - Project 21 : Review Proposal

[Asantha Thilina]

Hi all,

Thanks a lot for your valuable comments and feedback i done all the changes
as you suggested in feedback and submitted the final document to google
,modified google doc is in here[1]

[1]
https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing

Thanks,
Asantha

On Wed, Mar 23, 2016 at 8:08 PM, Asantha Thilina 
wrote:

> Hi Tharindu,
>
> thanks for the comment, sure i  do the modifications as suggested,
>
> Thanks,
> Asantha
>
> On Wed, Mar 23, 2016 at 6:54 PM, Tharindu Edirisinghe 
> wrote:
>
>> Hi Asantha,
>>
>> I've done some minor modifications to the doc. For the methods exposed
>> through the API, can you add them in a table to improve the readability.
>> (Chamila has suggested this already as a comment in the doc). You can have
>> some columns for Method Name, Return type, parameters, description.
>>
>> Once you do this, submit it to google because the deadline is tomorrow
>> for proposal submission.
>>
>> Thanks,
>> TharinduE
>>
>> On Wed, Mar 23, 2016 at 9:08 PM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> I modified my project proposal[1] in google doc, as you suggested i
>>> added function list which i am going to exposed to apis after modified the
>>> content  i shared the doc to summer of code.
>>> waiting for your feedback
>>> [1]
>>> https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing
>>>
>>> Thanks,
>>> Asantha
>>>
>>> On Tue, Mar 22, 2016 at 8:16 PM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Tharindu,

 thanks a lot for the feedbacks, sure i will modify the content of the
 proposal as suggested  and submit to google within today

 Thanks,
 Asantha


 On Wed, Mar 23, 2016 at 7:45 AM, Tharindu Edirisinghe <
 tharin...@wso2.com> wrote:

> Hi Asantha,
>
> I've added the latest proposal you've sent to google docs in [1]. As
> Chamila suggested, can you list down the methods that you expose in the 
> API
> (public methods in the userstore manager) in the proposal so that it is
> easy to understand the functionality of the userstore manager. Also it is
> better to submit the proposal to google now and update later if any
> modification is needed.
>
> [1]
> https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing
>
> Thanks,
> TharinduE
>
> On Mon, Mar 21, 2016 at 9:58 PM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Chamila,
>>
>> Thanks a lot for the feedback, sure i will update my proposal as you
>> suggested
>>
>> Thanks,
>> Asantha
>>
>> On Mon, Mar 21, 2016 at 9:18 AM, Chamila Wijayarathna <
>> cham...@wso2.com> wrote:
>>
>>> Hi Asantha,
>>>
>>> Looks good, please talk with Tharindu also before submitting the
>>> proposal. Even you submit your proposal, you can improve it until 25th.
>>>
>>> So if time permits, I would like to suggest you to add some details
>>> about what are the APIs and functions you are going to expose after
>>> developing this new user store manager, if you have already decided on
>>> them. Since you may have went through the codes of existing user store
>>> managers, you may already have an idea about what are the functions you
>>> need to exposed to outside. So if can add at least few functions you are
>>> going to expose with some details, it would make your proposal more
>>> attractive. Also I would like to suggest you to add link of github repo
>>> where you have started development. Also if you have written any blogs
>>> related to the project, mongoDB, etc. please mention them also in your
>>> proposal.
>>>
>>> Also I see some formatting issues and some dates has got repeated in
>>> your timeline, hope you will correct the when submitting proposal at 
>>> GSoC
>>> site.
>>>
>>> Cheers!
>>>
>>> On Mon, Mar 21, 2016 at 9:18 PM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Chamila,

 Thanks a lot for your valuable feedback as you suggested i
 corrected my project proposal and here i attached my finalize project
 proposal

 expecting your feedback

 Thanks,
 Asantha

 On Mon, Mar 21, 2016 at 5:44 AM, Chamila Wijayarathna <
 cham...@wso2.com> wrote:

> Hi Asantha,
>
> Thanks for sending your proposal. It seems to be in good shape,
> but I would like to suggest few more improvements.
>
>1.  You have mentioned you are implementing Custom User Store
>Manager by extending JDBCUserStoreManager. But actually you have 
> to extend
>

Re: [Dev] GSOC 2016 - Project 21 : Review Proposal

[Asantha Thilina]

Hi Tharindu,

thanks for the comment, sure i  do the modifications as suggested,

Thanks,
Asantha

On Wed, Mar 23, 2016 at 6:54 PM, Tharindu Edirisinghe 
wrote:

> Hi Asantha,
>
> I've done some minor modifications to the doc. For the methods exposed
> through the API, can you add them in a table to improve the readability.
> (Chamila has suggested this already as a comment in the doc). You can have
> some columns for Method Name, Return type, parameters, description.
>
> Once you do this, submit it to google because the deadline is tomorrow for
> proposal submission.
>
> Thanks,
> TharinduE
>
> On Wed, Mar 23, 2016 at 9:08 PM, Asantha Thilina  > wrote:
>
>> Hi Tharindu,
>>
>> I modified my project proposal[1] in google doc, as you suggested i added
>> function list which i am going to exposed to apis after modified the
>> content  i shared the doc to summer of code.
>> waiting for your feedback
>> [1]
>> https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing
>>
>> Thanks,
>> Asantha
>>
>> On Tue, Mar 22, 2016 at 8:16 PM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> thanks a lot for the feedbacks, sure i will modify the content of the
>>> proposal as suggested  and submit to google within today
>>>
>>> Thanks,
>>> Asantha
>>>
>>>
>>> On Wed, Mar 23, 2016 at 7:45 AM, Tharindu Edirisinghe <
>>> tharin...@wso2.com> wrote:
>>>
 Hi Asantha,

 I've added the latest proposal you've sent to google docs in [1]. As
 Chamila suggested, can you list down the methods that you expose in the API
 (public methods in the userstore manager) in the proposal so that it is
 easy to understand the functionality of the userstore manager. Also it is
 better to submit the proposal to google now and update later if any
 modification is needed.

 [1]
 https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing

 Thanks,
 TharinduE

 On Mon, Mar 21, 2016 at 9:58 PM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi Chamila,
>
> Thanks a lot for the feedback, sure i will update my proposal as you
> suggested
>
> Thanks,
> Asantha
>
> On Mon, Mar 21, 2016 at 9:18 AM, Chamila Wijayarathna <
> cham...@wso2.com> wrote:
>
>> Hi Asantha,
>>
>> Looks good, please talk with Tharindu also before submitting the
>> proposal. Even you submit your proposal, you can improve it until 25th.
>>
>> So if time permits, I would like to suggest you to add some details
>> about what are the APIs and functions you are going to expose after
>> developing this new user store manager, if you have already decided on
>> them. Since you may have went through the codes of existing user store
>> managers, you may already have an idea about what are the functions you
>> need to exposed to outside. So if can add at least few functions you are
>> going to expose with some details, it would make your proposal more
>> attractive. Also I would like to suggest you to add link of github repo
>> where you have started development. Also if you have written any blogs
>> related to the project, mongoDB, etc. please mention them also in your
>> proposal.
>>
>> Also I see some formatting issues and some dates has got repeated in
>> your timeline, hope you will correct the when submitting proposal at GSoC
>> site.
>>
>> Cheers!
>>
>> On Mon, Mar 21, 2016 at 9:18 PM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Chamila,
>>>
>>> Thanks a lot for your valuable feedback as you suggested i corrected
>>> my project proposal and here i attached my finalize project proposal
>>>
>>> expecting your feedback
>>>
>>> Thanks,
>>> Asantha
>>>
>>> On Mon, Mar 21, 2016 at 5:44 AM, Chamila Wijayarathna <
>>> cham...@wso2.com> wrote:
>>>
 Hi Asantha,

 Thanks for sending your proposal. It seems to be in good shape, but
 I would like to suggest few more improvements.

1.  You have mentioned you are implementing Custom User Store
Manager by extending JDBCUserStoreManager. But actually you have to 
 extend
AbstractUserStoreManager. I think you have done this correctly in 
 the code
you sent previously. Please correct this.
2. I think by custom user store manager, you have meant mongoDB
user store manager you are planning to implement, in most places. 
 Its
better to mention specifically as MongoDBUserStoreManager than 
 saying
custom user store manager.
3. You have mentioned about "Implement a proper encryption
mechanism to overcome the security hauls in 

Re: [Dev] GSOC 2016 - Project 21 : Review Proposal

[Tharindu Edirisinghe]

Hi Asantha,

I've done some minor modifications to the doc. For the methods exposed
through the API, can you add them in a table to improve the readability.
(Chamila has suggested this already as a comment in the doc). You can have
some columns for Method Name, Return type, parameters, description.

Once you do this, submit it to google because the deadline is tomorrow for
proposal submission.

Thanks,
TharinduE

On Wed, Mar 23, 2016 at 9:08 PM, Asantha Thilina 
wrote:

> Hi Tharindu,
>
> I modified my project proposal[1] in google doc, as you suggested i added
> function list which i am going to exposed to apis after modified the
> content  i shared the doc to summer of code.
> waiting for your feedback
> [1]
> https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing
>
> Thanks,
> Asantha
>
> On Tue, Mar 22, 2016 at 8:16 PM, Asantha Thilina  > wrote:
>
>> Hi Tharindu,
>>
>> thanks a lot for the feedbacks, sure i will modify the content of the
>> proposal as suggested  and submit to google within today
>>
>> Thanks,
>> Asantha
>>
>>
>> On Wed, Mar 23, 2016 at 7:45 AM, Tharindu Edirisinghe > > wrote:
>>
>>> Hi Asantha,
>>>
>>> I've added the latest proposal you've sent to google docs in [1]. As
>>> Chamila suggested, can you list down the methods that you expose in the API
>>> (public methods in the userstore manager) in the proposal so that it is
>>> easy to understand the functionality of the userstore manager. Also it is
>>> better to submit the proposal to google now and update later if any
>>> modification is needed.
>>>
>>> [1]
>>> https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing
>>>
>>> Thanks,
>>> TharinduE
>>>
>>> On Mon, Mar 21, 2016 at 9:58 PM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Chamila,

 Thanks a lot for the feedback, sure i will update my proposal as you
 suggested

 Thanks,
 Asantha

 On Mon, Mar 21, 2016 at 9:18 AM, Chamila Wijayarathna  wrote:

> Hi Asantha,
>
> Looks good, please talk with Tharindu also before submitting the
> proposal. Even you submit your proposal, you can improve it until 25th.
>
> So if time permits, I would like to suggest you to add some details
> about what are the APIs and functions you are going to expose after
> developing this new user store manager, if you have already decided on
> them. Since you may have went through the codes of existing user store
> managers, you may already have an idea about what are the functions you
> need to exposed to outside. So if can add at least few functions you are
> going to expose with some details, it would make your proposal more
> attractive. Also I would like to suggest you to add link of github repo
> where you have started development. Also if you have written any blogs
> related to the project, mongoDB, etc. please mention them also in your
> proposal.
>
> Also I see some formatting issues and some dates has got repeated in
> your timeline, hope you will correct the when submitting proposal at GSoC
> site.
>
> Cheers!
>
> On Mon, Mar 21, 2016 at 9:18 PM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Chamila,
>>
>> Thanks a lot for your valuable feedback as you suggested i corrected
>> my project proposal and here i attached my finalize project proposal
>>
>> expecting your feedback
>>
>> Thanks,
>> Asantha
>>
>> On Mon, Mar 21, 2016 at 5:44 AM, Chamila Wijayarathna <
>> cham...@wso2.com> wrote:
>>
>>> Hi Asantha,
>>>
>>> Thanks for sending your proposal. It seems to be in good shape, but
>>> I would like to suggest few more improvements.
>>>
>>>1.  You have mentioned you are implementing Custom User Store
>>>Manager by extending JDBCUserStoreManager. But actually you have to 
>>> extend
>>>AbstractUserStoreManager. I think you have done this correctly in 
>>> the code
>>>you sent previously. Please correct this.
>>>2. I think by custom user store manager, you have meant mongoDB
>>>user store manager you are planning to implement, in most places. Its
>>>better to mention specifically as MongoDBUserStoreManager than saying
>>>custom user store manager.
>>>3. You have mentioned about "Implement a proper encryption
>>>mechanism to overcome the security hauls in custom User store 
>>> Manager.".
>>>Can you be more specific on what are the security holes you are 
>>> talking
>>>about. AFAIK encryption mechanisms we are currently using are quite 
>>> ok and
>>>if there are no any strong reasons, I suggest you to follow the 
>>> existing
>>>mechanisms.

Re: [Dev] GSOC 2016 - Project 21 : Review Proposal

[Asantha Thilina]

Hi Tharindu,

I modified my project proposal[1] in google doc, as you suggested i added
function list which i am going to exposed to apis after modified the
content  i shared the doc to summer of code.
waiting for your feedback
[1]
https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing

Thanks,
Asantha

On Tue, Mar 22, 2016 at 8:16 PM, Asantha Thilina 
wrote:

> Hi Tharindu,
>
> thanks a lot for the feedbacks, sure i will modify the content of the
> proposal as suggested  and submit to google within today
>
> Thanks,
> Asantha
>
>
> On Wed, Mar 23, 2016 at 7:45 AM, Tharindu Edirisinghe 
> wrote:
>
>> Hi Asantha,
>>
>> I've added the latest proposal you've sent to google docs in [1]. As
>> Chamila suggested, can you list down the methods that you expose in the API
>> (public methods in the userstore manager) in the proposal so that it is
>> easy to understand the functionality of the userstore manager. Also it is
>> better to submit the proposal to google now and update later if any
>> modification is needed.
>>
>> [1]
>> https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing
>>
>> Thanks,
>> TharinduE
>>
>> On Mon, Mar 21, 2016 at 9:58 PM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Chamila,
>>>
>>> Thanks a lot for the feedback, sure i will update my proposal as you
>>> suggested
>>>
>>> Thanks,
>>> Asantha
>>>
>>> On Mon, Mar 21, 2016 at 9:18 AM, Chamila Wijayarathna 
>>> wrote:
>>>
 Hi Asantha,

 Looks good, please talk with Tharindu also before submitting the
 proposal. Even you submit your proposal, you can improve it until 25th.

 So if time permits, I would like to suggest you to add some details
 about what are the APIs and functions you are going to expose after
 developing this new user store manager, if you have already decided on
 them. Since you may have went through the codes of existing user store
 managers, you may already have an idea about what are the functions you
 need to exposed to outside. So if can add at least few functions you are
 going to expose with some details, it would make your proposal more
 attractive. Also I would like to suggest you to add link of github repo
 where you have started development. Also if you have written any blogs
 related to the project, mongoDB, etc. please mention them also in your
 proposal.

 Also I see some formatting issues and some dates has got repeated in
 your timeline, hope you will correct the when submitting proposal at GSoC
 site.

 Cheers!

 On Mon, Mar 21, 2016 at 9:18 PM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi Chamila,
>
> Thanks a lot for your valuable feedback as you suggested i corrected
> my project proposal and here i attached my finalize project proposal
>
> expecting your feedback
>
> Thanks,
> Asantha
>
> On Mon, Mar 21, 2016 at 5:44 AM, Chamila Wijayarathna <
> cham...@wso2.com> wrote:
>
>> Hi Asantha,
>>
>> Thanks for sending your proposal. It seems to be in good shape, but I
>> would like to suggest few more improvements.
>>
>>1.  You have mentioned you are implementing Custom User Store
>>Manager by extending JDBCUserStoreManager. But actually you have to 
>> extend
>>AbstractUserStoreManager. I think you have done this correctly in the 
>> code
>>you sent previously. Please correct this.
>>2. I think by custom user store manager, you have meant mongoDB
>>user store manager you are planning to implement, in most places. Its
>>better to mention specifically as MongoDBUserStoreManager than saying
>>custom user store manager.
>>3. You have mentioned about "Implement a proper encryption
>>mechanism to overcome the security hauls in custom User store 
>> Manager.".
>>Can you be more specific on what are the security holes you are 
>> talking
>>about. AFAIK encryption mechanisms we are currently using are quite 
>> ok and
>>if there are no any strong reasons, I suggest you to follow the 
>> existing
>>mechanisms.
>>4. It would be great if you can allocate 1-2 weeks for doing a
>>small research on how other NoSQL databases such as CouchDB, Neo4j 
>> can be
>>used to implement an user store in IS. By looking at your time line, I
>>think it would be possible to allocate some time for this in the 2nd 
>> half
>>of the programme. We can do this if time permits, but its better to 
>> mention
>>it in your proposal as optional (I believe it would make the project 
>> more
>>complete).
>>
>> Looking forward to see your proposal.
>>
>> Good Luck!
>>
>> On 

Re: [Dev] GSOC 2016 - Project 21 : Review Proposal

[Asantha Thilina]

Hi Tharindu,

thanks a lot for the feedbacks, sure i will modify the content of the
proposal as suggested  and submit to google within today

Thanks,
Asantha


On Wed, Mar 23, 2016 at 7:45 AM, Tharindu Edirisinghe 
wrote:

> Hi Asantha,
>
> I've added the latest proposal you've sent to google docs in [1]. As
> Chamila suggested, can you list down the methods that you expose in the API
> (public methods in the userstore manager) in the proposal so that it is
> easy to understand the functionality of the userstore manager. Also it is
> better to submit the proposal to google now and update later if any
> modification is needed.
>
> [1]
> https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing
>
> Thanks,
> TharinduE
>
> On Mon, Mar 21, 2016 at 9:58 PM, Asantha Thilina  > wrote:
>
>> Hi Chamila,
>>
>> Thanks a lot for the feedback, sure i will update my proposal as you
>> suggested
>>
>> Thanks,
>> Asantha
>>
>> On Mon, Mar 21, 2016 at 9:18 AM, Chamila Wijayarathna 
>> wrote:
>>
>>> Hi Asantha,
>>>
>>> Looks good, please talk with Tharindu also before submitting the
>>> proposal. Even you submit your proposal, you can improve it until 25th.
>>>
>>> So if time permits, I would like to suggest you to add some details
>>> about what are the APIs and functions you are going to expose after
>>> developing this new user store manager, if you have already decided on
>>> them. Since you may have went through the codes of existing user store
>>> managers, you may already have an idea about what are the functions you
>>> need to exposed to outside. So if can add at least few functions you are
>>> going to expose with some details, it would make your proposal more
>>> attractive. Also I would like to suggest you to add link of github repo
>>> where you have started development. Also if you have written any blogs
>>> related to the project, mongoDB, etc. please mention them also in your
>>> proposal.
>>>
>>> Also I see some formatting issues and some dates has got repeated in
>>> your timeline, hope you will correct the when submitting proposal at GSoC
>>> site.
>>>
>>> Cheers!
>>>
>>> On Mon, Mar 21, 2016 at 9:18 PM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Chamila,

 Thanks a lot for your valuable feedback as you suggested i corrected my
 project proposal and here i attached my finalize project proposal

 expecting your feedback

 Thanks,
 Asantha

 On Mon, Mar 21, 2016 at 5:44 AM, Chamila Wijayarathna  wrote:

> Hi Asantha,
>
> Thanks for sending your proposal. It seems to be in good shape, but I
> would like to suggest few more improvements.
>
>1.  You have mentioned you are implementing Custom User Store
>Manager by extending JDBCUserStoreManager. But actually you have to 
> extend
>AbstractUserStoreManager. I think you have done this correctly in the 
> code
>you sent previously. Please correct this.
>2. I think by custom user store manager, you have meant mongoDB
>user store manager you are planning to implement, in most places. Its
>better to mention specifically as MongoDBUserStoreManager than saying
>custom user store manager.
>3. You have mentioned about "Implement a proper encryption
>mechanism to overcome the security hauls in custom User store 
> Manager.".
>Can you be more specific on what are the security holes you are talking
>about. AFAIK encryption mechanisms we are currently using are quite ok 
> and
>if there are no any strong reasons, I suggest you to follow the 
> existing
>mechanisms.
>4. It would be great if you can allocate 1-2 weeks for doing a
>small research on how other NoSQL databases such as CouchDB, Neo4j can 
> be
>used to implement an user store in IS. By looking at your time line, I
>think it would be possible to allocate some time for this in the 2nd 
> half
>of the programme. We can do this if time permits, but its better to 
> mention
>it in your proposal as optional (I believe it would make the project 
> more
>complete).
>
> Looking forward to see your proposal.
>
> Good Luck!
>
> On Mon, Mar 21, 2016 at 5:15 PM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi All,
>>
>> here  i attached my project proposal for GSOC 2016 Project 21  for
>> your kind consideration,
>> I kindly request your feedback and thought on it.
>>
>> Thanks,
>> Asantha
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Chamila Dilshan Wijayarathna,*
> Software 

Re: [Dev] GSOC 2016 - Project 21 : Review Proposal

[Tharindu Edirisinghe]

Hi Asantha,

I've added the latest proposal you've sent to google docs in [1]. As
Chamila suggested, can you list down the methods that you expose in the API
(public methods in the userstore manager) in the proposal so that it is
easy to understand the functionality of the userstore manager. Also it is
better to submit the proposal to google now and update later if any
modification is needed.

[1]
https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing

Thanks,
TharinduE

On Mon, Mar 21, 2016 at 9:58 PM, Asantha Thilina 
wrote:

> Hi Chamila,
>
> Thanks a lot for the feedback, sure i will update my proposal as you
> suggested
>
> Thanks,
> Asantha
>
> On Mon, Mar 21, 2016 at 9:18 AM, Chamila Wijayarathna 
> wrote:
>
>> Hi Asantha,
>>
>> Looks good, please talk with Tharindu also before submitting the
>> proposal. Even you submit your proposal, you can improve it until 25th.
>>
>> So if time permits, I would like to suggest you to add some details about
>> what are the APIs and functions you are going to expose after developing
>> this new user store manager, if you have already decided on them. Since you
>> may have went through the codes of existing user store managers, you may
>> already have an idea about what are the functions you need to exposed to
>> outside. So if can add at least few functions you are going to expose with
>> some details, it would make your proposal more attractive. Also I would
>> like to suggest you to add link of github repo where you have started
>> development. Also if you have written any blogs related to the project,
>> mongoDB, etc. please mention them also in your proposal.
>>
>> Also I see some formatting issues and some dates has got repeated in your
>> timeline, hope you will correct the when submitting proposal at GSoC site.
>>
>> Cheers!
>>
>> On Mon, Mar 21, 2016 at 9:18 PM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Chamila,
>>>
>>> Thanks a lot for your valuable feedback as you suggested i corrected my
>>> project proposal and here i attached my finalize project proposal
>>>
>>> expecting your feedback
>>>
>>> Thanks,
>>> Asantha
>>>
>>> On Mon, Mar 21, 2016 at 5:44 AM, Chamila Wijayarathna 
>>> wrote:
>>>
 Hi Asantha,

 Thanks for sending your proposal. It seems to be in good shape, but I
 would like to suggest few more improvements.

1.  You have mentioned you are implementing Custom User Store
Manager by extending JDBCUserStoreManager. But actually you have to 
 extend
AbstractUserStoreManager. I think you have done this correctly in the 
 code
you sent previously. Please correct this.
2. I think by custom user store manager, you have meant mongoDB
user store manager you are planning to implement, in most places. Its
better to mention specifically as MongoDBUserStoreManager than saying
custom user store manager.
3. You have mentioned about "Implement a proper encryption
mechanism to overcome the security hauls in custom User store Manager.".
Can you be more specific on what are the security holes you are talking
about. AFAIK encryption mechanisms we are currently using are quite ok 
 and
if there are no any strong reasons, I suggest you to follow the existing
mechanisms.
4. It would be great if you can allocate 1-2 weeks for doing a
small research on how other NoSQL databases such as CouchDB, Neo4j can 
 be
used to implement an user store in IS. By looking at your time line, I
think it would be possible to allocate some time for this in the 2nd 
 half
of the programme. We can do this if time permits, but its better to 
 mention
it in your proposal as optional (I believe it would make the project 
 more
complete).

 Looking forward to see your proposal.

 Good Luck!

 On Mon, Mar 21, 2016 at 5:15 PM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi All,
>
> here  i attached my project proposal for GSOC 2016 Project 21  for
> your kind consideration,
> I kindly request your feedback and thought on it.
>
> Thanks,
> Asantha
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Chamila Dilshan Wijayarathna,*
 Software Engineer
 Mobile:(+94)788193620
 WSO2 Inc., http://wso2.com/

>>>
>>>
>>
>>
>> --
>> *Chamila Dilshan Wijayarathna,*
>> Software Engineer
>> Mobile:(+94)788193620
>> WSO2 Inc., http://wso2.com/
>>
>
>


-- 

Tharindu Edirisinghe
Software Engineer | WSO2 Inc
Platform Security Team
Blog : tharindue.blogspot.com
mobile : +94 775181586
___
Dev mailing 

Re: [Dev] GSOC 2016 - Project 21 : Review Proposal

[Asantha Thilina]

Hi Chamila,

Thanks a lot for the feedback, sure i will update my proposal as you
suggested

Thanks,
Asantha

On Mon, Mar 21, 2016 at 9:18 AM, Chamila Wijayarathna 
wrote:

> Hi Asantha,
>
> Looks good, please talk with Tharindu also before submitting the proposal.
> Even you submit your proposal, you can improve it until 25th.
>
> So if time permits, I would like to suggest you to add some details about
> what are the APIs and functions you are going to expose after developing
> this new user store manager, if you have already decided on them. Since you
> may have went through the codes of existing user store managers, you may
> already have an idea about what are the functions you need to exposed to
> outside. So if can add at least few functions you are going to expose with
> some details, it would make your proposal more attractive. Also I would
> like to suggest you to add link of github repo where you have started
> development. Also if you have written any blogs related to the project,
> mongoDB, etc. please mention them also in your proposal.
>
> Also I see some formatting issues and some dates has got repeated in your
> timeline, hope you will correct the when submitting proposal at GSoC site.
>
> Cheers!
>
> On Mon, Mar 21, 2016 at 9:18 PM, Asantha Thilina  > wrote:
>
>> Hi Chamila,
>>
>> Thanks a lot for your valuable feedback as you suggested i corrected my
>> project proposal and here i attached my finalize project proposal
>>
>> expecting your feedback
>>
>> Thanks,
>> Asantha
>>
>> On Mon, Mar 21, 2016 at 5:44 AM, Chamila Wijayarathna 
>> wrote:
>>
>>> Hi Asantha,
>>>
>>> Thanks for sending your proposal. It seems to be in good shape, but I
>>> would like to suggest few more improvements.
>>>
>>>1.  You have mentioned you are implementing Custom User Store
>>>Manager by extending JDBCUserStoreManager. But actually you have to 
>>> extend
>>>AbstractUserStoreManager. I think you have done this correctly in the 
>>> code
>>>you sent previously. Please correct this.
>>>2. I think by custom user store manager, you have meant mongoDB user
>>>store manager you are planning to implement, in most places. Its better 
>>> to
>>>mention specifically as MongoDBUserStoreManager than saying custom user
>>>store manager.
>>>3. You have mentioned about "Implement a proper encryption mechanism
>>>to overcome the security hauls in custom User store Manager.".  Can you 
>>> be
>>>more specific on what are the security holes you are talking about. AFAIK
>>>encryption mechanisms we are currently using are quite ok and if there 
>>> are
>>>no any strong reasons, I suggest you to follow the existing mechanisms.
>>>4. It would be great if you can allocate 1-2 weeks for doing a small
>>>research on how other NoSQL databases such as CouchDB, Neo4j can be used 
>>> to
>>>implement an user store in IS. By looking at your time line, I think it
>>>would be possible to allocate some time for this in the 2nd half of the
>>>programme. We can do this if time permits, but its better to mention it 
>>> in
>>>your proposal as optional (I believe it would make the project more
>>>complete).
>>>
>>> Looking forward to see your proposal.
>>>
>>> Good Luck!
>>>
>>> On Mon, Mar 21, 2016 at 5:15 PM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi All,

 here  i attached my project proposal for GSOC 2016 Project 21  for your
 kind consideration,
 I kindly request your feedback and thought on it.

 Thanks,
 Asantha


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> *Chamila Dilshan Wijayarathna,*
>>> Software Engineer
>>> Mobile:(+94)788193620
>>> WSO2 Inc., http://wso2.com/
>>>
>>
>>
>
>
> --
> *Chamila Dilshan Wijayarathna,*
> Software Engineer
> Mobile:(+94)788193620
> WSO2 Inc., http://wso2.com/
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSOC 2016 - Project 21 : Review Proposal

[Chamila Wijayarathna]

Hi Asantha,

Looks good, please talk with Tharindu also before submitting the proposal.
Even you submit your proposal, you can improve it until 25th.

So if time permits, I would like to suggest you to add some details about
what are the APIs and functions you are going to expose after developing
this new user store manager, if you have already decided on them. Since you
may have went through the codes of existing user store managers, you may
already have an idea about what are the functions you need to exposed to
outside. So if can add at least few functions you are going to expose with
some details, it would make your proposal more attractive. Also I would
like to suggest you to add link of github repo where you have started
development. Also if you have written any blogs related to the project,
mongoDB, etc. please mention them also in your proposal.

Also I see some formatting issues and some dates has got repeated in your
timeline, hope you will correct the when submitting proposal at GSoC site.

Cheers!

On Mon, Mar 21, 2016 at 9:18 PM, Asantha Thilina 
wrote:

> Hi Chamila,
>
> Thanks a lot for your valuable feedback as you suggested i corrected my
> project proposal and here i attached my finalize project proposal
>
> expecting your feedback
>
> Thanks,
> Asantha
>
> On Mon, Mar 21, 2016 at 5:44 AM, Chamila Wijayarathna 
> wrote:
>
>> Hi Asantha,
>>
>> Thanks for sending your proposal. It seems to be in good shape, but I
>> would like to suggest few more improvements.
>>
>>1.  You have mentioned you are implementing Custom User Store Manager
>>by extending JDBCUserStoreManager. But actually you have to extend
>>AbstractUserStoreManager. I think you have done this correctly in the code
>>you sent previously. Please correct this.
>>2. I think by custom user store manager, you have meant mongoDB user
>>store manager you are planning to implement, in most places. Its better to
>>mention specifically as MongoDBUserStoreManager than saying custom user
>>store manager.
>>3. You have mentioned about "Implement a proper encryption mechanism
>>to overcome the security hauls in custom User store Manager.".  Can you be
>>more specific on what are the security holes you are talking about. AFAIK
>>encryption mechanisms we are currently using are quite ok and if there are
>>no any strong reasons, I suggest you to follow the existing mechanisms.
>>4. It would be great if you can allocate 1-2 weeks for doing a small
>>research on how other NoSQL databases such as CouchDB, Neo4j can be used 
>> to
>>implement an user store in IS. By looking at your time line, I think it
>>would be possible to allocate some time for this in the 2nd half of the
>>programme. We can do this if time permits, but its better to mention it in
>>your proposal as optional (I believe it would make the project more
>>complete).
>>
>> Looking forward to see your proposal.
>>
>> Good Luck!
>>
>> On Mon, Mar 21, 2016 at 5:15 PM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> here  i attached my project proposal for GSOC 2016 Project 21  for your
>>> kind consideration,
>>> I kindly request your feedback and thought on it.
>>>
>>> Thanks,
>>> Asantha
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Chamila Dilshan Wijayarathna,*
>> Software Engineer
>> Mobile:(+94)788193620
>> WSO2 Inc., http://wso2.com/
>>
>
>


-- 
*Chamila Dilshan Wijayarathna,*
Software Engineer
Mobile:(+94)788193620
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSOC 2016 - Project 21 : Review Proposal

[Asantha Thilina]

Hi Chamila,

Thanks a lot for your valuable feedback as you suggested i corrected my
project proposal and here i attached my finalize project proposal

expecting your feedback

Thanks,
Asantha

On Mon, Mar 21, 2016 at 5:44 AM, Chamila Wijayarathna 
wrote:

> Hi Asantha,
>
> Thanks for sending your proposal. It seems to be in good shape, but I
> would like to suggest few more improvements.
>
>1.  You have mentioned you are implementing Custom User Store Manager
>by extending JDBCUserStoreManager. But actually you have to extend
>AbstractUserStoreManager. I think you have done this correctly in the code
>you sent previously. Please correct this.
>2. I think by custom user store manager, you have meant mongoDB user
>store manager you are planning to implement, in most places. Its better to
>mention specifically as MongoDBUserStoreManager than saying custom user
>store manager.
>3. You have mentioned about "Implement a proper encryption mechanism
>to overcome the security hauls in custom User store Manager.".  Can you be
>more specific on what are the security holes you are talking about. AFAIK
>encryption mechanisms we are currently using are quite ok and if there are
>no any strong reasons, I suggest you to follow the existing mechanisms.
>4. It would be great if you can allocate 1-2 weeks for doing a small
>research on how other NoSQL databases such as CouchDB, Neo4j can be used to
>implement an user store in IS. By looking at your time line, I think it
>would be possible to allocate some time for this in the 2nd half of the
>programme. We can do this if time permits, but its better to mention it in
>your proposal as optional (I believe it would make the project more
>complete).
>
> Looking forward to see your proposal.
>
> Good Luck!
>
> On Mon, Mar 21, 2016 at 5:15 PM, Asantha Thilina  > wrote:
>
>> Hi All,
>>
>> here  i attached my project proposal for GSOC 2016 Project 21  for your
>> kind consideration,
>> I kindly request your feedback and thought on it.
>>
>> Thanks,
>> Asantha
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Chamila Dilshan Wijayarathna,*
> Software Engineer
> Mobile:(+94)788193620
> WSO2 Inc., http://wso2.com/
>


Proposal (2) (1).docx
Description: MS-Word 2007 document
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSOC 2016 - Project 21 : Review Proposal

[Chamila Wijayarathna]

Hi Asantha,

Thanks for sending your proposal. It seems to be in good shape, but I would
like to suggest few more improvements.

   1.  You have mentioned you are implementing Custom User Store Manager by
   extending JDBCUserStoreManager. But actually you have to extend
   AbstractUserStoreManager. I think you have done this correctly in the code
   you sent previously. Please correct this.
   2. I think by custom user store manager, you have meant mongoDB user
   store manager you are planning to implement, in most places. Its better to
   mention specifically as MongoDBUserStoreManager than saying custom user
   store manager.
   3. You have mentioned about "Implement a proper encryption mechanism to
   overcome the security hauls in custom User store Manager.".  Can you be
   more specific on what are the security holes you are talking about. AFAIK
   encryption mechanisms we are currently using are quite ok and if there are
   no any strong reasons, I suggest you to follow the existing mechanisms.
   4. It would be great if you can allocate 1-2 weeks for doing a small
   research on how other NoSQL databases such as CouchDB, Neo4j can be used to
   implement an user store in IS. By looking at your time line, I think it
   would be possible to allocate some time for this in the 2nd half of the
   programme. We can do this if time permits, but its better to mention it in
   your proposal as optional (I believe it would make the project more
   complete).

Looking forward to see your proposal.

Good Luck!

On Mon, Mar 21, 2016 at 5:15 PM, Asantha Thilina 
wrote:

> Hi All,
>
> here  i attached my project proposal for GSOC 2016 Project 21  for your
> kind consideration,
> I kindly request your feedback and thought on it.
>
> Thanks,
> Asantha
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Chamila Dilshan Wijayarathna,*
Software Engineer
Mobile:(+94)788193620
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev