GNU-devel ELPA - oauth2

oauth2 Atom Feed

Description
OAuth 2.0 Authorization Protocol
Latest
oauth2-0.17.0.20240830.100757.tar (.sig), 2024-Aug-30, 20.0 KiB
Maintainer
Julien Danjou <julien@danjou.info>
Website
https://elpa.gnu.org/packages/oauth2.html
Browse ELPA's repository
CGit or Gitweb
Badge

To install this package from Emacs, use package-install or list-packages.

Full description

Implementation of the OAuth 2.0 draft.

The main entry point is `oauth2-auth-and-store' which will return a token
structure.  This token structure can be then used with
`oauth2-url-retrieve-synchronously' or `oauth2-url-retrieve' to retrieve
any data that need OAuth authentication to be accessed.

If the token needs to be refreshed, the code handles it automatically and
store the new value of the access token.

Old versions

oauth2-0.16.0.20240830.70956.tar.lz2024-Aug-304.03 KiB
oauth2-0.16.0.20221221.81302.tar.lz2024-Mar-313.36 KiB
oauth2-0.16.0.20210219.101633.tar.lz2021-Feb-193.31 KiB
oauth2-0.15.0.20201201.213140.tar.lz2020-Dec-143.30 KiB

News

Summary of changes to oauth2.el
-------------------------------

(For changes of 0.16 and older please check the git history of the
repository of oauth2.el.)

* 0.17

** Changes to plstore id generation and needs to reacquire refresh_token

The generation of plstore id used to include `auth-url', `token-url',
and `scope'.  Now `client-id' is also included.  This is required to
support multiple accounts of some providers which use the same
`auth-url', `token-url', and `scope' (e.g. Gmail), or the generated
plstore id is not unique amount accounts.  Adding `client-id' solves
this problem.

The hash function of calculating the plstore id has also changed from
MD5 to SHA512 to be more secure.

As a result, users of oauth2.el will need to redo the authentication
process to get a new refresh_token when upgrading from older version
to 0.17.

# Local variables:
# mode: outline
# End: