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
The goal of the registry is to provide a method for probes to register, login and update their probe metadata, such that we are able to implement access control for gaining access to the tor test helper configuration. This was implemented at a time when:
We needed the push notification tokens as we were using our own custom push notification solution instead of countly
We would be giving out private bridges to probes
Both of these are no longer true and so the login, register and update no longer serve a true purpose.
That said, probes expect these endpoints to work and so we still need to somehow serve responses for them otherwise they risk breaking. That's why we implemented in the API what is effectively a noop for these endpoints, however we haven't yet made the switch over to them (see: https://github.com/ooni/backend/blob/master/api/ooniapi/probe_services.py#L438).
Since we have quite a bit of work related to authenticating probes as part of the anonymous credentials project, it would probably be wise to decouple this piece from the monolith backend and integrate it into a separate component that we deploy using the new pattern.
This will set us up nicely to be able to then place the anonymous credentials code inside of it. Moreover, since probes are submitting metadata about their probe as part of this request, we can also use this endpoint to measure inconsistencies related to probe metadata and public IPs of probes (as per: ooni/ooni.org#1646)
This is related to being able to discontinue ams-ps: #892.
The text was updated successfully, but these errors were encountered:
hellais
changed the title
Port ams-ps related endpoints over to AWS API
Port ams-ps probe-services related endpoints over to new pattern for deployment in ECS
Jan 8, 2025
The
ams-ps.ooni.nu
host runs some the old OONI Orchestra component: https://github.com/ooni/orchestra.In reality only the "registry" component of orchestra is being used, this is what the nginx configuration on backend-fsn looks like:
The goal of the registry is to provide a method for probes to register, login and update their probe metadata, such that we are able to implement access control for gaining access to the tor test helper configuration. This was implemented at a time when:
Both of these are no longer true and so the login, register and update no longer serve a true purpose.
That said, probes expect these endpoints to work and so we still need to somehow serve responses for them otherwise they risk breaking. That's why we implemented in the API what is effectively a noop for these endpoints, however we haven't yet made the switch over to them (see: https://github.com/ooni/backend/blob/master/api/ooniapi/probe_services.py#L438).
Since we have quite a bit of work related to authenticating probes as part of the anonymous credentials project, it would probably be wise to decouple this piece from the monolith backend and integrate it into a separate component that we deploy using the new pattern.
This will set us up nicely to be able to then place the anonymous credentials code inside of it. Moreover, since probes are submitting metadata about their probe as part of this request, we can also use this endpoint to measure inconsistencies related to probe metadata and public IPs of probes (as per: ooni/ooni.org#1646)
This is related to being able to discontinue ams-ps: #892.
The text was updated successfully, but these errors were encountered: