| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
it doesn't hurt anything even though it's not super necessary for plain
logins, and it's more convenient to access without needing to
deconstruct the enum value
|
| |
|
|
|
|
|
| |
i can't exchange refresh tokens for access tokens without knowing the
webface oauth configuration either, so this strategy also won't work.
the server actually needs to only receive access tokens, and request the
web server to refresh them as needed.
|
| |
|
|
|
|
|
|
|
|
| |
the local client needs to receive the code and send it directly to the
server, which handles the rest of the oauth flow (because the client
doesn't have the server's oauth configuration, so it can't do the
exchange itself), but the web client needs to receive the code and
exchange it for a token and send that token to the server (because the
server doesn't have the web server's oauth configuration, so it can't do
the exchange itself)
|
| |
|
|
|
| |
so that frontends that want to handle logins themselves can still have
the client handle the connection process
|
| |
|
|
| |
so that we can use the client outside of a direct terminal context
|
| | |
|
| |
|
