User
User Management and Authentication
Last updated
Was this helpful?
User Management and Authentication
Last updated
Was this helpful?
To create new User(s) in the system. API supports bulk creation with max limit as defined in the UserReq. Please note that either whole batch succeeds or fails, there's no partial batch success. To create one user, please pass array with one user object.
Users can be created based on the roles. Users with types as SYSTEM and EMPLOYEE can create other users if their RBAC mapping provides them the permission. Users with CITIZEN type can only create themselves, while EMPLOYEE and SYSTEM type users can also create other EMPLOYEES and CITIZENS.
User registration will always be a two step process, where this API will create a non authenticated user (without password) and after verification (using OTP) other user details (including password) can be updated using update user API to complete the user registration process.
/_create
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
This API will update all user related details based on their type. Following rules apply -
/_update
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
Search and get user(s) based on defined search criteria. Currently search parameters are only allowed as HTTP query params. In case multiple parameters are passed user will be searched as an AND combination of all the parameters. Maximum result size is restricted based on the maxlength of Users as defined in UserRes model.
By default results will be sorted by UserName
/_search
The unique user name of the User.
True will be set in cases where only active users are needed and False will be set when inactive users are needed and no value will be set when all users are needed.
List of Unique Id of User
Defines the type of user. Possible values are as per type enum defined in User object.
roles assigned to the user(roleCodes).Search response will have all users having all roles specified in the request.
parameter to indicate whether UserDetails should be included as a part of User object in the response
Number of records returned.
Page number
User results will be sorted by name ascending by default if this parameter is not provided.
This API used for update the password after login
/password/_update
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
Existing password
New password
Unique Identifier of the tenant to which user primarily belongs
This API used for reset the password when user forgot his password by getting otp Reference through registerd mobile number,
/password/nologin/_update
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
otp reference number which sent to registered mobile
Registered User name
New password
Unique Identifier of the tenant to which user primarily belongs