summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2021-10-01gui: listen for settings changesVivien Kraus
2021-10-01client: add display methods for account and clientVivien Kraus
2021-10-01gui: Bind the settings to schemeVivien Kraus
2021-10-01client: rename client-key-pair and client-redirect-uri by dropping 'client-'Vivien Kraus
2021-10-01build-system: change to the correct shebang for help2man laterVivien Kraus
2021-10-01gui settings: have a static pool of other accountsVivien Kraus
If we create them dynamically, we won’t be able to delete them due to a hole in GLib: https://gitlab.gnome.org/GNOME/glib/-/issues/993
2021-10-01gui: Add a gsettings schemaVivien Kraus
2021-10-01XML: support list of objectsVivien Kraus
2021-10-01Define an XML-loadable meta-classVivien Kraus
2021-09-23JWK: allow a string for #:crvVivien Kraus
2021-09-22Use anonymous-http-request from (webid-oidc parameters) everywhereVivien Kraus
2021-09-21OIDC configuration: use GOOPS and document itVivien Kraus
2021-09-21Serialize and deserialize tokens to and from SXMLVivien Kraus
2021-09-21JWS: use GOOPSVivien Kraus
2021-09-21doc: Add a word on the front page.Vivien Kraus
2021-09-21JWK: serialize and deserialize to and from SXMLVivien Kraus
2021-09-21JWK: the default signature algorithm "alg" is now a key parameterVivien Kraus
2021-09-21JWK: add an explicit value for kty in the JSON representationVivien Kraus
2021-09-21JWK: document it, and use GOOPSVivien Kraus
2021-09-17Application state: make it fully immutableVivien Kraus
2021-09-15Start a GUIVivien Kraus
2021-09-15Client API: add a pretty printerVivien Kraus
2021-09-15Add an application state class to handle multi-threaded actionsVivien Kraus
2021-09-14Restructure the client APIVivien Kraus
The client API had several problems: - using records instead of GOOPS means that we aren’t flexible enough to introduce accounts protected by a password, for a multi-user application; - saving the user database to disk means we can’t have a proper immutable API; - it was difficult to predict when the users database would change, and inform the user interface about this change; - it had two different ways to negociate an access token, one when we had a refresh token and one when we did not; - it was supposed to either use account objects or a subject / issuer pair, now we only use account objects.
2021-09-13Client: use http-request instead of http-get and http-postVivien Kraus
2021-09-13Update hook: do not set the number of coresVivien Kraus
2021-09-13Fix a test nameVivien Kraus
2021-09-13Use a larger size for the iconVivien Kraus
GNOME shell will rasterize it as 48x48 in the app overview otherwise.
2021-09-13Don’t save an account if it does not have a subjectVivien Kraus
I added a function to log in for the first time, so that we don’t have to store an account for which we know we will need to jump through the authorization endpoint hoops.
2021-09-13Add GNOME application iconVivien Kraus
2021-09-13Update translationsVivien Kraus
2021-09-13Add missing importVivien Kraus
2021-09-13Fix a syntax errorVivien Kraus
2021-09-13Fix a syntax errorVivien Kraus
2021-09-13Fix syntax errorVivien Kraus
2021-09-13Add missing moduleVivien Kraus
2021-09-13fix function nameVivien Kraus
2021-09-13Fix syntax errorVivien Kraus
2021-09-13Fix a test nameVivien Kraus
2021-09-13Fix function nameVivien Kraus
2021-09-13Remove dead codeVivien Kraus
2021-09-13Fix typoVivien Kraus
2021-09-13Add missing moduleVivien Kraus
2021-09-13Fix a syntax error and missing moduleVivien Kraus
2021-09-13Fix syntax errorVivien Kraus
2021-09-13Add missing moduleVivien Kraus
2021-09-13Fix a syntax errorVivien Kraus
2021-09-13Fix a syntax errorVivien Kraus
2021-09-13Fix a syntax errorVivien Kraus
2021-09-13Fix a syntax errorVivien Kraus