interledger / rafiki

An open-source, comprehensive Interledger service for wallet providers, enabling them to provide Interledger functionality to their users.
https://rafiki.dev/
Apache License 2.0
233 stars 83 forks source link

[Auth] Move interaction routes to a different port #2649

Closed sabineschaller closed 4 months ago

sabineschaller commented 5 months ago

Context

The auth package currently has the GNAP routes and the interaction routes on the same port. The GNAP routes need to be exposed to the world while the interaction routes do not. Hence, we'd like to move the interaction routes to their own port.

To clarify:

Todos

golobitch commented 5 months ago

Isn't problematic only accept/reject route?

These two are most problematic in my view. For example, if Rafiki Auth is exposed, then on the checkout of Rafiki Boutique, I can use probably any payment pointer I want. Because for accepting grant, I only need interaction and nonce. For /finish route, that is probably ok to be exposed right? Because redirect url is specified in grant if I am not mistaken. So it will be always redirected to correct URL. There can be issue only in case of MITM attack.

Just a food for thought :)

golobitch commented 5 months ago

@sabineschaller on the link that you provided (https://openpayments.dev/apis/auth-server/), I cannot see any routes.

I can take this ticket if we specify what routes should be exposed and what not.

Suggestion: Leave as it is with the exception of /accept and /reject API call. These two are IMHO most sensitive