search

SURFnet / surf-token-based-access

1 stars 1 forks source link

webdav-mounter + ts-oauth2-server-example in phase-3 PoC #53

Closed michielbdejong closed 1 month ago

michielbdejong commented 1 month ago

This is a running log of issues I'm working through to build the client - AS interaction for the PoC of phase 3.

First one: http://localhost:5173/authorize?response_type=code&client_id=xxxxxxx&redirect_uri=http%3A%2F%2Flocalhost&scope=%22contacts.read%20contacts.write%22&state=abcdefghijklmnopqrstuvwxyz123456789&code_challenge=92d3b56942866d1edf02c33339b7c3dc37c6201282bb238cb47f0d3289f28a93f1bdd8af6ca9913aed0c4c&code_challenge_method=S256 is a 404. I think I should add or enable the /authorize route somehow.

michielbdejong commented 1 month ago

That's fixed (in the dev branch of this repo) and scope now set to webdav-folder. Next: show an authorize dialog

michielbdejong commented 1 month ago

The scopes dialog is unfinished. It doesn't display the scopes. Maybe that's fine because I'm going to do it completely differently anyway.

When the user arrives at the scopes page, they should be redirected immediately to the resource helper. Probably already from the Authorization controller.

michielbdejong commented 1 month ago

got the basic components working and know my way around now. Note that this is only client (running on laptop) - AS (running on vultr.pondersource.org) - IDP (i.e. SRAM), the RS (owncloud) has not been added yet.

follow-up issues: