Managing user access across systems is a common enterprise requirement. In this implementation, Oracle Integration Cloud (OIC) acts as the middleware between CORS and the Workforce System (WFS) to synchronize users and their roles.
Flow 1: WFS to CORS – User and Role Export
This scheduled OIC integration runs periodically to extract user information from WFS.
Process
- OIC Scheduler triggers the integration.
- Lists all available files from the WFS SFTP location.
- For each file, downloads the content.
- Writes the files to the OIC Embedded SFTP server.
- Delete file from WFS SFTP.
- CORS picks up the files using a service account.
- List of Users
- User with Roles
Flow 2: CORS to WFS – User Provisioning and Role Management
This integration exposes a REST API that allows CORS to request user provisioning or role assignment/removal in WFS.
Process
- CORS sends user details and roles through a REST request.
- OIC validates and transforms the data into the format required by WFS.
- Creates the appropriate provisioning file.
- Places the file in the WFS SFTP location for processing.
Supported Actions
- Create User
- Assign Role
- Remove Role
This approach provides a simple file-based integration mechanism while maintaining system decoupling.
Request feed:
{
"users": {
"ReqNo": "123123",
"loginID": "user010",
"UserEmail": "sendmail-test-discard@oracle.com",
"Roles": [
{
"Action": "ADD",
"RoleName": "Company General User"
},
{
"Action": "REMOVE",
"RoleName": "Company Roster Creator"
}
]
}
}
Response:
{
"Status": "RECEIVED/ERROR",
"Message": "",
"users": {
"ReqNo": "123123",
"loginID": "user010",
"UserEmail": "user010@oracle.com",
"Roles": [
{
"Action": "ADD",
"RoleName": "Project Administrator"
},
{
"Action": "REMOVE",
"RoleName": "Project Administrator"
}
]
}
}
File fileds required by wfs: <InterfaceNumber>_USER_ROLES_<datetime>
Flow 3: CORS to WFS – Provisioning Status Validation
After provisioning requests are submitted, CORS can verify the processing status through another REST service exposed by OIC.
Process
- CORS sends the User ID and Role information.
- OIC obtains an authentication token from WFS.
- Calls WFS APIs to retrieve current users and assigned roles.
- Compares the requested data with the actual data in WFS.
Response Logic
- Success – User exists and all requested roles are assigned.
- Pending – User exists but roles are not yet assigned.
- Error – User does not exist in WFS.
This validation mechanism provides real-time visibility into provisioning status and helps CORS track completion of access requests.
Request : same as previous flow
Response:
{
"users": [
{
"Status": "SUCCESS/ERROR/PENDING",
"Message": "",
"ReqNo": "123123",
"loginID": "user010"
}
]
}
Get Token:
Request payload: {"grant_type":""}
Response payload: {"access_token":""}
Mapping: map "client_credentials" to grant_type.
Get User Logs:
Sample response:
{
"updateSequence": [
{
"recordId": "...",
"dataChange": "MERGE",
"userId": "...",
"externalId": "21144",
"generalRoles": [
"TA-AS_EMPLOYEE",
"TA-CHANGE_OWN_PASSWORD",
"TA-DESKTOP_EMPLOYEE_TIME_OFF_REQUESTS",
"TA-MOBILE_CLOCK_USER",
"TA-MOBILE_USER"
],
"groupRights": [
{
"id": "TA-2146425995",
"roleId": "TA-DELEGATOR_GROUP",
"type": "EMPLOYEE_GROUP"
}
],
"errors": [
"You would have been more ..."
],
"nextCursor": "..."
}
]
}
Mapping:
1. Authorization : Bearer <token>
2. Count : 5000 (this limit is on the number of records to retrieve.)
Code logic for response:
Benefits
- Automated user and role synchronization.
- Secure file transfer through SFTP.
- REST-based provisioning interface.
- Real-time status validation.
- Reduced manual user administration effort.
- Reliable integration between CORS and WFS using Oracle Integration Cloud.
This blog provides an end-to-end overview of the user provisioning and role synchronization framework implemented using OIC between CORS and Workforce System (WFS).
