[FINERACT-726] Changes to /authentication API's to pass data as part of request body

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.0
• Fix Version/s: 1.4.0
• Labels: 2019-mifos-gsoc gsoc p1 volunteer
• Assignee: Michael Vorburger
• Reporter: Vishwas Babu A J
• Created: 06/Mar/19 02:43
• Updated: 13/May/21 05:06
• Resolved: 10/Jan/20 15:35

Description

Fineract supports authentication either using Basic auth or Oauth. The initial authentication is done using the endpoints described at https://demo.openmf.org/api-docs/apiLive.htm#authentication_basicauth and https://demo.openmf.org/api-docs/apiLive.htm#authentication_oauth 

Both rely on passing the username and password as URL query parameters.

Ex, the endpoint for /authentication is 

POST  : https://localhost:8443/fineract-provider/api/v1/authentication?username=mifos&password=password&tenantIdentifier=default

 

We would want to change the same to

POST https://localhost:8443/fineract-provider/api/v1/authentication?tenantIdentifier=default

and pass the username and password as apart of the post body in json format.

Ex:

{
"username":"mifos",
"password":"password"
}

 

After making this change, the APIdocs and integration test cases would have to be updated accordingly 

Issue Links

• blocks: FINERACT-677 Hide Sensitive contents in xml files and logs
• is duplicated by: FINERACT-677 Hide Sensitive contents in xml files and logs
• is duplicated by: FINERACT-629 Authentication API endpoint forces username and password as URL params
• is required by: FINERACT-629 Authentication API endpoint forces username and password as URL params
• links to: GitHub Pull Request #678