search

ConsumerDataStandardsAustralia / standards-maintenance

This repository houses the interactions, consultations and work management to support the maintenance of baselined components of the Consumer Data Right API Standards and Information Security profile.
41 stars 9 forks source link

Recover from lost client registration #545

Closed Smoovsky closed 2 years ago

Smoovsky commented 2 years ago

I'm not sure if this is the right place to ask, as this could be either a Consumer Data Standard question or a Data Holder Implementation question.

That standard states that "Duplicate registrations are not permitted so attempts to create a registration which already exists MUST return an HTTP 400 error." Whilst it's not impossible that the data recipient failed to receive and save the registration result due to some transient network/database error or lost the detail of existing registration in some edge cases. In that case, I don't see any plan B other than contacting the data holder's support and asking them to either give the existing registration detail or simply delete the old registration.

perlboy commented 2 years ago

In that case, I don't see any plan B other than contacting the data holder's support and asking them to either give the existing registration detail or simply delete the old registration.

That is exactly what the expected behaviour is.

Client Registrations are so rare (once) I'm unclear what the cost/benefit win is of having some backup method for, arguably, the most complex technical action in the CDR.

Smoovsky commented 2 years ago

That is exactly what the expected behaviour is.

Thanks for your prompt reply. If that's intended then the data recipient just needs to be careful with keeping existing registrations.

perlboy commented 2 years ago

Yes, Recipients must be careful with their registrations because there are legal requirements on the organisation if they are lost (data deletion, arrangement revocations etc).