Big Picture User Experience
Officially test and document the feature added to datapump in OASyS 7.6R4 to allow pulling from an untrusted, lower security zone.
Detailed Description
Customer wants to datapump data from an untrusted domain into a trusted domain.
There are many use-cases that rely on this feature.
History
PMFR-281: Bi-Directional Datapump across untrusted domains
Was almost included in a 2018 release
Documentation was taken out, and it appears the fix to make it work went out as a hotfix
Project team have successfully configured it to work, and are maintaining doc describing it
TFS# 282096 was a fix for datapump via RCS, and was delivered as a 2018 HF.
Beta documentation was created, but not included in the hotfix, or 2018 SP3, or 2021, and is very specific to the one custom table the customer is using it for.
To pull data instead of push doesn’t require a bunch of extra configuration mainly just reversing the connections so that the source is using the DAL (through RCS_XFER) and the destination is local.
Acceptance Criteria
The ability for datapump running in a trusted domain to pull data from a non-trusted domain is tested for all baseline tables, and documented.
Business Value
Productize (document, test, hardened, genericize) the solution that the project delivered to ENB, to be able to state full support.
Target Version
TBD
Customer has a solution in place for 2020 and 2021, and company has agreed to support it there.
Customer, Project, and Deadline Details
It is very important to ENB that our documentation be complete
Customers System / Architecture
- Size: Small, Med, and Large
- Topology: Single site, Multi Site, and Enterprise
- Any Unique configuration to note?:
Split Realtimes.
- Has this functionality been delivered before?: Yes, see History section above.
Out of Scope
Pushing data from an untrusted domain into a trusted domain is not and will never be supported.
Assumptions
Code is mostly done.
Effort is mainly documentation, testing, hardening and any generalizations needed to productize the feature.
Dependencies
None
PSR - Performance, Scalability, Resilience
None - the code is in use in production, and is passing acceptances tests.
NFR - Non-Functional Requirements
All that is required is proper test coverage, and documentation.
Risks/Mitigations
The final solution needs to continue to pass all our strict cyber-security guidelines.