Overview
We're seeing an increase in 403s due to anti-AI lockdowns of website scraping which we get caught up in. If the Check tool can't access the data due to a 403, we should make sure we explain this (I think we already do) but then offer them our IP addresses to send to their IT team to whitelist us.
We should use Gov Notify to do this - validating that the email address we are sending to us a legitimate LPA one (we'll need to figure out how that works for Nat Parks and Dev Co that may not use gov.uk). This is also a good test for the future moving to Gov Notify for other aspects of the data adding journey.
As a starting point, we can use the canned JIRA response but that should be looked at by designers. Not sharing on this public board as the whole point is that we don't want these IP addresses available on the open internet for others to mimic as us.
We could also try and introduce this onto the LPA Dashboard when there are collection errors that are 403. May need a separate ticket for this - again, would need to validate that the person doing the action is from the LPA which might get tricky.
Overview
We're seeing an increase in 403s due to anti-AI lockdowns of website scraping which we get caught up in. If the Check tool can't access the data due to a 403, we should make sure we explain this (I think we already do) but then offer them our IP addresses to send to their IT team to whitelist us.
We should use Gov Notify to do this - validating that the email address we are sending to us a legitimate LPA one (we'll need to figure out how that works for Nat Parks and Dev Co that may not use gov.uk). This is also a good test for the future moving to Gov Notify for other aspects of the data adding journey.
As a starting point, we can use the canned JIRA response but that should be looked at by designers. Not sharing on this public board as the whole point is that we don't want these IP addresses available on the open internet for others to mimic as us.
We could also try and introduce this onto the LPA Dashboard when there are collection errors that are 403. May need a separate ticket for this - again, would need to validate that the person doing the action is from the LPA which might get tricky.