Hi Badal,
i am struggling exactly with the same thing here - and haven't found a solution yet.
As a temporary fix, (which i dislike very much) i have special user configured in AD - and since all request are going through the servlet, that user credentials are stored on a server in a separate config file, and are used each time during request to jenkins json api.
This temp solution is fine to query info (e.g. get job lists, statuses, definitions etc) but when it comes down to running a job it is bad, since i want to see what job was triggered by what user.
Please if you find a solution let me know.
cheers,
Rob