You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Task Change nro-extractor to poll namesdb instead of accepting http requests
Detailed Description
Currently nro-extractor moves Name Request from NRO to NameX based on receiving a http POST/PUT from namesdb.
There was an outage in moving NRs from NRO to NameX based on a security change on the edge routers that removed support for TLS 1.0/1.1. We believe that the patches to use TLS1.2 have not been applied to namesdb, resulting in namesdb not being able to send https POST/PUTS to namex.
As we may see more such changes or lack thereof to the legacy environments, it was decided that nro-extractor should be reworked into a poller that pulls NRs from NRO to NameX, much like nro-updater runs as a CRON job sending changes back to NRO.
The text was updated successfully, but these errors were encountered:
Task Change nro-extractor to poll namesdb instead of accepting http requests
Detailed Description
Currently nro-extractor moves Name Request from NRO to NameX based on receiving a http POST/PUT from namesdb.
There was an outage in moving NRs from NRO to NameX based on a security change on the edge routers that removed support for TLS 1.0/1.1. We believe that the patches to use TLS1.2 have not been applied to namesdb, resulting in namesdb not being able to send https POST/PUTS to namex.
As we may see more such changes or lack thereof to the legacy environments, it was decided that nro-extractor should be reworked into a poller that pulls NRs from NRO to NameX, much like nro-updater runs as a CRON job sending changes back to NRO.
The text was updated successfully, but these errors were encountered: