HaaS Flex Transition Runsheets
This is the index of runsheets that describe all of the migration tasks in the HaaS Flex Transition Plan.
info
It's important to note that not all steps apply to every one of our customers. We will work with you to identify what is necessary for your setup and guide you through the process.
Biza ID Federationβ
- Customers must have their Biza ID Federation enabled on their supported Identity Provider
- Customers must have setup RBAC authorisations for their staff with roles for HaaS Manager and Product Manager where required.
Product Manager Migrationβ
info
This is required by all banking customers that currently maintain their PRD in PRD Admin.
warning
This requires Biza ID federation to be finalised.
- Customer needs to Import product data into the Product Manager subscription
- Customer needs to Verify data is correct and ready to be the source of truth for their HaaS PRD
HaaS Space Magellan Releaseβ
warning
This requires Biza ID Federation to be finalised.
- Biza will upgrade to the Magellan Release for your HaaS space. This includes:
- Removes PRD Admin for Product Manager
- Replaces HaaS Admin with HaaS Manager that is authenticated via Biza ID
- Requires adapter to implement
Get Endpoint Meta V3
Adapter Reconnectionsβ
- Customer will need to migrate their implementations to the OAuth Adapter Profile with those customers who are on a deprecated security profile.
- Customers will need to reconnect their Data Adapter connections to the new HaaS space where required:
Management APIβ
- Customer will need to migrate their implementations to the public + OAuth Management API profile
DNS Changesβ
- Update DNS to point at our new consolidated nameservers / canonical names for the HaaS Spaces
- Customers will need to update their DNS for Biza Delegated Zone setups
- Customers will need to update their DNS for Customer Managed DNS setups
SIEM Log Changesβ
info
These changes are required only for production spaces as we do not have SIEM logs exporting in non-production spaces.
- Customers who are using SIEM in AWS will need to update their SIEM to allow logs from another AWS account