SURFnet / surf-token-based-access

1 stars 1 forks source link

Lodging Intent #16

Closed michielbdejong closed 11 months ago

michielbdejong commented 11 months ago

This pattern benefits from the domain specific knowledge in the RS and keeps the AS very clean and generic. As a consequence, there must be a properly protected interface between AS and RS.

https://bitbucket.org/openid/fapi/src/master/Financial_API_Lodging_Intent.md#markdown-header-642-rs-provides-intent-implementation

michielbdejong commented 11 months ago

Via https://medium.com/oauth-2/transaction-authorization-or-why-we-need-to-re-think-oauth-scopes-2326e2038948

michielbdejong commented 11 months ago

And "Pushed Request Object"

I'll do some more web search!

michielbdejong commented 11 months ago

It's explained well in https://www.youtube.com/watch?v=U9i7YaN8v9c - just don't put the scopes through the front channel. It's only a part of our solution though. See https://github.com/pondersource/surf-token-based-access/blob/main/token-based-access%20flows.pdf for next steps

michielbdejong commented 5 months ago