After upgrading the above library version, there might be chance that an issue occur for RequestInfo creation because of change in variable type, please go through all java files including JUnit test cases before pushing the changes.
The above library version need to be upgraded in the dependant module also.
For Example: If water service call the property service and property service is calling user service for owner details then the version of above library need to be upgraded in property service pom file also.
Demand generation changes:
At service level or calculator service level where demand generation process take place, there payer details value must be pass in plain form. And these user details must get through SYSTEM user.
Create a system user in the particular environment and make sure that system user has role INTERNAL_MICROSERVICE_ROLE. Use the curl mentioned below:
Create a method/ function which call the user search API to get the user details in plain form, in that call pass the userInfo of the user with INTERNAL_MICROSERVICE_ROLE
For reference follow the below code snippet
private User getPlainOwnerDetails(RequestInfo requestInfo, String uuid, String tenantId){
User userInfoCopy = requestInfo.getUserInfo();
StringBuilder uri = new StringBuilder();
uri.append(configs.getUserHost()).append(configs.getUserSearchEndpoint()); // URL for user search call
Map<String, Object> userSearchRequest = new HashMap<>();
tenantId = tenantId.split("\\.")[0];
//Creating role with INTERNAL_MICROSERVICE_ROLE
Role role = Role.builder()
.name("Internal Microservice Role").code("INTERNAL_MICROSERVICE_ROLE")
.tenantId(tenantId).build();
//Creating userinfo with uuid and role of internal micro service role
User userInfo = User.builder()
.uuid(configs.getEgovInternalMicroserviceUserUuid())
.type("SYSTEM")
.roles(Collections.singletonList(role)).id(0L).build();
requestInfo.setUserInfo(userInfo);
// Setting user search criteria
userSearchRequest.put("RequestInfo", requestInfo);
userSearchRequest.put("tenantId", tenantId);
userSearchRequest.put("uuid",Collections.singletonList(uuid));
User user = null;
try {
LinkedHashMap<String, Object> responseMap = (LinkedHashMap<String, Object>) serviceRequestRepository.fetchResult(uri, userSearchRequest);
List<LinkedHashMap<String, Object>> users = (List<LinkedHashMap<String, Object>>) responseMap.get("user");
String dobFormat = "yyyy-MM-dd";
// parsing the user response and coverting object into User.class pojo
notificationUtil.parseResponse(responseMap,dobFormat);
user = mapper.convertValue(users.get(0), User.class);
} catch (Exception e) {
throw new CustomException("EG_USER_SEARCH_ERROR", "Service returned null while fetching user");
}
requestInfo.setUserInfo(userInfoCopy);
return user;
}
Report Configuration Changes:
For the report where PII data is present and decryption is required, such report definition must have UUID values from user table in the query result.
And the Source column section of the report definition must have mention of the UUID column and for that entry, showColumn flag should be set as false.
And the base sql query in the report config should be written in such a way that in the query it must have the user uuid.
In the config, for name: uuid
Here replace uuid with the name of the column containing the user’s uuid in the query’s output.
Example:
SELECT emp_data.id as id,
emp_data.name as name,
emp_data.uuid as uuid,
desigmap_def.code as designation,
deptmap_def.code as department,
emp_data.employeestatus as status
FROM emp_data ehe
inner join eg_user eu ON ehe.uuid = eu.uuid
In the report config where PII data is present and decryption is required, add this new filed in the report config decryptionPathId. And in the Security Policy mdms file, must have the model configuration from the particular report. And the value of key model in Security Policy mdms file and decryptionPathId in a report must be same.
For the searcher result where PII data is present and decryption is required, such searcher definition must have UUID values from user table in the query result. The base sql query in the searcher config should be written in such a way that in the query it must have the user uuid.
I searcher result, where data are coming from user table and to get those value in decrypted form, then in searcher config these following filed decryptionPathIdmust be present. And the Security Policy mdms file, must have the model configuration from the particular searcher config. And the value of key model in Security Policy mdms file and decryptionPathId in searcher config must be same.
For details information on Security Policy MDMS file refer this document.
