| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Much better for dark theme too
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This is for 2.x servers that return an empty refresh token after refreshing
|
|
|
|
|
|
|
|
|
|
This is for V1 configs
|
|
If an error is non-nil, the data is guaranteed to contain a value
For discovery we do not explicitly forward errors (TODO, log in
the wrapper?). However, when building in release mode, we have embedded
disco so even if we get an error we should have guaranteed that it contains a value
|
|
This additional bookkeeping is not needed now because we have contexts
|
|
|
|
This implements a token handler for OAuth tokens. Clients can use the SetTokenHandler
function in exports to set a token handler.
It needs two arguments, a getter and a setter. The getter is a callback with three arguments:
- The server to get the tokens for, in types.server.current as JSON
- The output buffer
- The output buffer maximum length
The tokens should be written to the output buffer with maximum
length. The type should be types.server.Tokens and be marshalled as
JSON. If no tokens are available, leave the output buffer intact
The token setter is a callback with two arguments:
- The server for which to set the tokens for, in types.server.Current as JSON
- The tokens, defined in types.server.Tokens as JSON
Breaking changes:
- No more tokens as arguments, was already deprecated in previous commits
- Tokens are no longer returned in types.server.Configuration
|
|
|
|
|
|
|
|
BREAKING CHANGES:
- The following functions need a special "cookie" as the first argument
- Add server (also now has an extra int as last argument, if non 0 run no callbacks, useful for preprovisioned servers)
- Get config
- Set secure location
- Disco servers
- Disco organizations
- Cleanup
- Renew session
- Start failover
Removed functions:
- "CancelOAuth", "CancelFailover" replaced by "CookieCancel"
- SecureLocationList, removed because the secure internet server
from ServerList() now has the locations embedded in the JSON
A cookie is a specialized context that can be used for cancellation
and sending values across a channel. Cancel OAuth and Cancel failover
functions have thus been removed. Instead, create a cookie with
"CookieNew", pass it to the function as the first argument and when you
want to cancel, run "CookieCancel".
The functions mentioned above use network requests, or some other
long running procedure. Even though we have a timeout set to 10
seconds for failover and network requests, it might make sense to make
this longer and just have clients cancel the request.
Cookies that have been created with "CookieNew" must be freed with
CookieDelete, which cancels the cookie and then deletes the underlying
handle.
Because cookies have a channel associated with them, they are used for
replying to state callbacks. When you receive an ASK_PROFILE or
ASK_LOCATION request, you get the same cookie back that you have
created when passed to the function (key "cookie" in the state
data). Reply with your answer (the profile or location) with
"CookieReply" passing in the cookie as first argument and the data as
second.
This means that SetProfileID and SetSecureLocation should
now only be used when not in a state callback. E.g. just changing the
profile or location when triggered by the user.
Finally, when a cookie is canceled, the error that is returned by the
function inherits from the Go context cancellation error:
https://pkg.go.dev/context#pkg-variables ("context canceled")
|
|
|
|
Much easier to oversee and it forces me to keep the client type as
small as possible. This also uses the cookie for cancellation
We also no longer require tokens inside arguments. We will later
implement them with callbacks
|
|
|
|
Used as a specialized context in state callbacks and for cancellation
|
|
|
|
- Pass contexts
- Have separate packages for e.g. custom, institute and secure
- internet servers, profiles....
- Return types from the public ./types package with a Public() method
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Linux requires su for `ip4:icmp` pings. Windows does not support `udp4`
pings.
Signed-off-by: Simon Rozman <simon@rozman.si>
|
