Evalai: Restrict the update profile API Endpoint from updating username

[deshraj]

Currently, django-rest-auth provides the functionality to update the username with the update profile API Endpoint. We want to restrict this since we don't want a user to update his username once he has created his account.

For more details about the API endpoint, look at http://django-rest-auth.readthedocs.io/en/latest/api_endpoints.html#basic

[deshraj]

Related to #863

[yadavankit]

@deshraj can I take it up?

[deshraj]

@yadavankit Sure. :)

[mayank-agarwal-96]

@deshraj @yadavankit Is anyone still working on this or can I take this one?

[deshraj]

@mayank-agarwal-96 Yeah, you can work on it. :)

[yadavankit]

@deshraj ohh, I just forgot this issue... my bad 😅 @mayank-agarwal-96 yeah go on bro...you can take this up :)

[guyandtheworld]

Hi, I'm a bit new to restful services using django, and I guess that with a bit of learning I could solve this issue, where would be the best place to start using rest for evalai?

[yadavankit]

Hey @isht3 Django REST Framework Documentation would be a good place to start learning about how REST is implemented in EvalAI.

[guyandtheworld]

@taranjeet @yadavankit I'm currently in the process of learning django REST, I'd like to inform that I'll be back for bigger contributions to CloudCV after I'm done with a personal project of mine.

[deshraj]

@isht3 Sounds good. Thanks for informing. :)

[guyandtheworld]

@deshraj Can I start working on this? :)

[RishabhJain2018]

yes sure. Assigning this to you.

[guyandtheworld]

Hi, @deshraj @RishabhJain2018 To update the username after creation of account we should do a PUT request to /api/auth/user/, right? I'd like to test this for a bit, would it be best to do it through cURL or drf-docs?

[RishabhJain2018]

@isht3 Please refer here for the command https://pvcarrera.github.io/general/2015/03/18/curl.html. Moreover , you can usePostmanclient for the same. Let me know if you still have doubts.

[guyandtheworld]

@RishabhJain2018 I'll look into it! :smile:

[guyandtheworld]

@RishabhJain2018 Hi, I have analysed the issue. Since only the PUT or PATCH request to the /auth/user/ which contains username should be restricted, it would require writing a view to check the parameters passed during a PUT or PATCH request, if it doesn't edit the username then passes then pass it onto rest_auth, right?