Describe new BN Hub/BNI strategy

[Kaineatthelab]

A new strategy has been approved to work with our partners like Finance. We need a description of the strategy that can be used for partners and go in a Briefing Note as well.

• Continue the build of the API solution • Run both the API solution and BNHUB in parallel for 18 months • Finance onboards to the API solution with their timing • Decommission the BN HUB when all parties are ready and Keep BNI going for the foreseeable future

[Kaineatthelab]

Hello,

Below are notes and action items captured from yesterday’s discussion - please let me know if anything requires adjustment. For reference, I have also attached the CRA’s BN Change Release Scope document.

ATTENDEES: Executive Director & Registrar - Kaine Sparks Home Team - Ian Bott, Patrick Wei, David McKinnon, Patty Stemkens, Wael Helal, Thayne Werdal, David Roberts Modernization Team - Linda McClung, Thor Wolpert Digital Delivery – Dwayne Gordon (REGRETS), Dani Williamson

Discussion: • Meeting called to discuss CRA integrations and see if everyone is on the same page between the modernization team and the home team. • Modernization team has indicated and communicated to CRA in the last BN partner meeting: o To account for Partners’ needs, we plan to keep the Legacy BN services running and fully functional for the foreseeable future, 12-18 months (BN Hub and messaging) o The Registry (our modernized system) will also start to use the new CRA API Gateway. o Concerning partners, in any place where BN Hub partners need information obtained only via the BN API, the new Registry will also publish that to the Hub. o Bulk/Async data currently sent to the HUB via SFTP will continue to be delivered and processed that way. • CRA’s Scope of BN Changes for October 2022 Release doc requires more technical specifications for the home and modernization teams can prepare for the CRA API Gateway release and PKI docs. o First bullet under CRA's scope document talks about decommissioning the BN Hub in October - this is not accurate. BC is not planning to decommission the BN Hub in this timeframe, nor is BC planning to change the legacy Hub messaging to connect to the new CRA API Gateway. We expect to be able to continue legacy messaging while Modernization builds out their solution. o Document indicates an October 2022 timeline where BC will be decommissioning their BN Hub and moving it to the new BC Registries system, which will utilize CRA web services using RESTful protocol through the CRA’s API Gateway. o Changes will only impact inbound web services sent to CRA from BC. There will be no changes to the existing outbound Broadcast Message/FTP service from CRA to BC. BC will be the 1st partner to pilot the use of the CRA’s API Gateway. o CRA also indicates that they understand that existing web services functionality between CRA and BC Ministries will remain the same. Ministries will interact with CRA via the BC Registry. • PKI certs requests CRA has requested are for devices, currently we have these device certificates that are to do with file transfer vs the API interface. We’ll need CRA to provide clarity; If it’s the CRA API Gateway then the devices, IPs and testing would be through the modernization team, not the home team. • Home Team has identified that resources will be required to repair technical issues with the BN Hub for it to function satisfactorily for partners for another 12-18 months.
• BC Registries will present CRA with a new recommendation for continuing the BN Hub and the CRA API Gateway. • BC Registries sends SP/GP messages to CRA via the GCP (need permanent ICP addresses), and we send other messages to CRA via the BN Hub. CRA sends SP/GP messages back to API & Hub. Question: Modernization team would like to clarify if legacy messages sent from the BN Hub would be returned to both the BN Hub & CRA API Gateway.

Action Items: • BC Registries team will assemble an RFC this week to document a recommendation, technical specifications and organizational notes and timing for a BC Registries system that could receive messages from the BN Hub and the API Gateway. An agreement with CRA may need to be created. o Thor, Patrick (and perhaps Linda) will draft the RFC this week o Dani will schedule a follow-up meeting for group discussion o Kaine will present the final RFC to CRA to discuss options and timelines

[daniwilliamson]

@thorwolpert has prepared the RFC - CRA BN REST API Dataflow: https://docs.google.com/document/d/1Xxomr1pZZsAi_FvH9_xqrjDK09DCNHtxOke-4dOyl24/edit#heading=h.1tcw5uc4xbr9.

Thor noted: Some of our definitions around partners: https://github.com/bcgov/entity/blob/master/rfcs/rfc-bnhub-modernization.md This may change, as John Jordan was suggesting we have some conversations on the future of OrgBook, as it is no longer picking up much in the way of Permits and may just merge into some future version of the Registry Search. I have some thoughts in progressive access to business infom so will write up an RFC or Slides to see if that's a direction of interest.

Thor is on holiday w/o July 25 - 30 and will be preparing the RFC next week when he returns.

[daniwilliamson]

On July 15, CRA confirmed to Dwayne and Dani there are no foreseeable issue with our delaying the BN Hub and continuing to operate the BN legacy systems in tandem with the modern system for the next 12-18 months. CRA confirm there should be zero disruption to the SOAP calls - and cautiously optimistic there will not be any issues out to 2024.

July 19, spoke with Linda and CRA confirmed by email their understanding that BC will not be moving to the Gateway as part of the CRA October release. BC expects to have some services ready to test in September, and will target a move to the Gateway for May 2023. This will involve a limited number of BC partners, the exact numbers and which ones to be confirmed. Based on this information, CRA will work with their IT (and BC) to develop a timeline and milestones to achieve the May 2023 release date.

PKI documents are outstanding pending IP and device names.

[daniwilliamson]

@thorwolpert can you provide an update on the RFC, or slides, or one-pager? Sounds like we're looking for a one-pager type document that CRA and our team can agree on with timelines and scope (Kaine noted that Elizabeth Carlyle is expecting this).

[daniwilliamson]

@thorwolpert @lmcclung Concerning the RFC draft, titled RFC - CRA BN REST API Dataflow: https://docs.google.com/document/d/1Xxomr1pZZsAi_FvH9_xqrjDK09DCNHtxOke-4dOyl24/edit#heading=h.1tcw5uc4xbr9. Can you help me understand the audience? Was it written for the CRA, and the purpose is to help BC Registries "to determine where parallel messaging between the new and legacy BN services will take place"?

Or, is this RFC draft document intended to outline scope for changes of work required to be done by Thor's team to accommodate the CRA's new REST API? I've read the document several times and can not tell. Please let me know asap as Kaine has requested a document for discussion with CRA and I'm struggling to understand the draft RFC context. Thx!

[daniwilliamson]

https://app.zenhub.com/files/157936592/1ae10d44-9540-4f15-a14c-7c83bd8548ac/download

@thorwolpert @lmcclung @Kaineatthelab A brief CRA API Gateway one-pager (plus timeline) is attached for your consideration. Please add/modify to the scope, purpose, assumptions, and timeline where you see fit. Let me know if a quick meeting would be more efficient for you. Once our internal team agrees on this doc, we’ll share it with CRA to ensure we all align. CRA has requested a meeting with Dwayne and I on Wednesday, October 5. Would be ideal to have alignment prior to mtg.

[daniwilliamson]

@thorwolpert @lmcclung @Kaineatthelab

CRA API Gateway Testing doc is attached. Testing proposed for November 2022 and release in February 2023.

Scope, assumptions and timelines were discussed with CRA on October 5. @lmcclung and @thorwolpert, please confirm these dates and assumptions, let us know if there are any other considerations, and we'll provide the updated doc to CRA for their approval.

https://app.zenhub.com/files/157936592/a8a96116-8db7-47d7-b50f-fb45b6b61def/download

TIMELINE • Oct. 6, 2022 - BC Registries (BCR) approval of CRA Testing Plan doc. • Oct. 9, 2022 - General agreement between CRA and BC Registries on testing workflow. • Oct. 11-14, 2022 - BC Registries review of revised test plan • Oct. 24-28, 2022 - CRA review of revised test plan • Oct. 28, 2022 - CRA testing environment open to BCR • Nov. 4, 2022 - BCR accesses API Gateway test environment and begins testing with a simulated partner. • Nov. 4, 2022 - CRA security review begins. • Nov. 10, 2022- Testing completed. • Jan. 31, 2022 - Memorandum signed between CRA and BC Registries • Feb. 5/6*, 2023 - Launch. BC Registries can begin using the production API Gateway and can release corporations. • Feb. 12, 2023 - BC Registries first release date.

ASSUMPTIONS • Workflow - If BC Registries begins testing in November 2022, completes testing by the first week of November, it can start using the API Gateway for production data in February 2023. This timeline does not impact BC Registries project capital as it is in the same quarter. • Service flow – The proposed changes will not impact CRA’s FTP Outbound Messaging for BC Registries. The change applies to the Inbound webservices from BC to CRA. BC Registries is both a consumer of the API Gateway and BN REST Webservices, as well as a broker for the information to flow through to other BC partners. The follow-up (down the road) is to remove BC Registries from the picture, and have the other BC Partners come direct to the CRA API Gateway. At that time, BC Registries becomes a consumer of the services only. o Flow once the changes happen to enable CRA’s External API Gateway and BN REST Webservices: Request Comes from BC Registries -> CRA API Gateway -> BN Webservices -> CRA API Gateway -> BC Registries o Flow will change when it comes to other BC Partners (i.e., BC WorkSafeBC): Request comes from BC Partner system -> BC Registries -> CRA API Gateway -> BN Webservices -> CRA API Gateway -> BC Registries -> BC Partner System • Simulated Test Partner - CRA’s connection will be with the BC Registries and CRA will depend on BC Registries to manage the connection with its partners. CRA’s Risk Management Team and API centre of expertise have confirmed that BC Registries may simulate a test partner, provided BC Registries can ensure security of the test end point (traceability, detection, and prevention of compromise) and document this in a Memorandum of Understanding that includes an explanation of how BC Registries will manage this, such as a token is passed between the Registry and the partner. • Testing Environment Accessibility – CRA will leave the testing environment open to BC Registries during the security review and into January 2023. • Test Environment – CRA will maintain testing and production environments going forward, they are not abandon-ware. • Security Review - CRA has a 3-month security review process. • CRA Maintenance - Mid-oct is biannual CRA maintenance on old BN messaging. Which there is no impact to this API Gateway testing.

Linda's comments included in updated attachment. @thorwolpert, as per Linda's email, could you please review and provide feedback.

[pwei1018]

@thorwolpert Can we mark this ticket done and close?