Nathan Lie

Closing as a consequent of the reasoning in https://github.com/interledger/rafiki/issues/576. > Closing for now due to AS-RS being in a trusted zone

What version of OpenAPI (or what commit of the AS) was this tried on? I have it working on this branch that's pending a merge: https://github.com/interledger/rafiki/tree/nl-use-split-openapi

I tried this using your grant request. The only things I changed where: * `client.key.jwk.kid`: To `localhost` so it would point to my mock account provider * `client.key.jwk.x`: To the...

> @njlie Want to open a pull request in [interledger/open-payments](https://github.com/interledger/open-payments) removing/fixing whatever `access` restriction are causing problems (maybe just use the `uniqueItems`/`maxItems` for now), and update this to use the...

Removed a task from the issue because Rafiki is treating key registry management as an implementation detail now

I checked the extension's product page with our Mozilla dev account, where it says it's been approved for Firefox for Android...

@JoblersTune Is there any other setup that needs to be done on the postgres instance? I had to manually create the `hydra` database and the `hydra_user` user but I'm stuck...

> I'm thinking of picking this up since this is in the `createTokenIntrospectionMiddleware` that would directly be part of > > * [Decouple Open Payments from Rafiki's `backend` and `auth`...

> What do you think about original PR review comment? > > > Should we create an openPaymentsServerErrorMiddleware like we do in backend to catch all of the GNAPErrors to...

Would it also make sense to include adding `401` responses to the AS endpoints for invalid signatures to the scope of this issue?