solid-contrib / monetization-tests Goto Github PK

This issue provides visibility into Renovate updates and their statuses. Learn more

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency @types/jest to v27.4.1
• Update dependency eslint to v8.14.0
• Update dependency eslint-plugin-prettier to v3.4.1
• Update dependency prettier to v2.6.2
• Update typescript-eslint monorepo to v5.20.0 (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• Update Node.js to v16 (node, @types/node)
• Update dependency eslint-config-prettier to v8
• Update dependency eslint-plugin-prettier to v4
• Update dependency node-fetch to v3
• Update dependency ws to v8 (ws, @types/ws)
• Update jest monorepo to v27 (major) (jest, ts-jest)
• Click on this checkbox to rebase all open PRs at once

• Check this box to trigger a request for Renovate to run again on this repository

Similar to anyone logged in
we introduce "anyone who paid"; we'll need to pick a predicate similar to acl:AuthenticatedAgent, for instance acl:PayingAgent.

One test: 401 if you haven't authenticated at all and authenticating may help

• If the current agent is not authenticated
• Even if the ACL doc for a resource contains an authorization with acl:agentClass acl:PayingAgent
• If there is at least one other authorization that would accept the request for some authenticated user
• But based on just the other authorizations the request would be rejected for unauthenticated users

Then the server should give a 401 response like it normally would

One test: 402 if you haven't authenticated and paying is the only way in

• If the current agent is not authenticated
• And the ACL doc for a resource contains an authorization with acl:agentClass acl:PayingAgent
• And there are no other authorization that would accept the request for any authenticated user
• And the request would be rejected for unauthenticated users

Then the server should give a 402 response, along with a WWW-Pay header, for instance:

WWW-Pay: ilp-stream-webid realm=<realm>

Another test: 402 if you haven't paid

• If the current agent is authenticated but didn't pay
• And the ACL doc for a resource contains an authorization with acl:agentClass acl:PayingAgent
• And based on that authorization the request would be accepted for authenticated users who paid
• And based on just the other authorizations the request would be rejected for the current user

Then the server should give a 402 response, along with a WWW-Pay header, for instance:

WWW-Pay: ilp-stream-webid realm=<realm>

Another test: OK if paid

• If the current agent is authenticated as a WebID who has already paid
• And the ACL doc for a resource contains an authorization with acl:agentClass acl:PayingAgent
• And based on that authorization the request would be accepted for authenticated users who paid

Then the server should give a 200 response

To obtain webid-oidc-dpop credentials for https://payment.processor/challenge/lil3aepieghaiG3A#ok it would be good if you could somehow:

• discover what needs paying
• (pretend to) pay it via ILP/STREAM
• POST your STREAM receipt somewhere
• get your webid-oidc-dpop credentials in the response

One test to add: Vanity Payment Pointer (no slash)

If for instance https://solidtestsuite.solidcommunity.net/profile/card contains a triple:

<#me> <http://paymentpointers.org/ns#PaymentPointer> "$example.com"

Then https://solidtestsuite.solidcommunity.net/.well-known/pay
Should redirect with a 302
to https://example.com/.well-known/pay

Another one: Vanity Payment Pointer (with slash)

If for instance https://solidtestsuite.solidcommunity.net/profile/card contains a triple:

<#me> <http://paymentpointers.org/ns#PaymentPointer> "$example.com/foo/bar"

Then https://solidtestsuite.solidcommunity.net/.well-known/pay
Should redirect with a 302
to https://example.com/foo/bar