oidc-agent 1.2.3

Adds the DEEP OIDC Provider

oidc-agent 1.2.2

Removed https://perun.elixir-czech.cz/oidc/ from issuer.config, because this instance will shutdown. It will keep running till end of April. Already registered clients can be moved to https://login.elixir-czech.org/oidc/ To do so contact elixir.

New clients should be registered at https://login.elixir-czech.org/oidc/

oidc-agent 1.2.1

• Support for providing the device authorization endpoint manually

oidc-agent 1.2.0

Features

Support for Authorization Code Flow

By supporting the Authorization Code Flow oidc-agent is now usable with almost
any OpenID Provider. Supported Providers are, among others: B2Access, EGI-Checkin, Elixir,
Google and The Human Brain Project (HBP).

Support for Device Flow

oidc-agent supports now the Device Flow. A second device can be used for the
client authorization. Does not require a web browser on the device where
oidc-agent is running.

Possibility to specify flow to be used

When using oidc-gen to generate a new account configuration the --flow option
can be used to specify the flow used to obtain the refresh token. Multiple
values can be given to express priorities.

Support for Scopes

When using oidc-gen to generate a new account configuration scopes can be
provided to adjust the default scopes. Scopes are checked with the OpenID
Provider; provided scopes that are not supported by the OpenID Provider are
automatically discarded

When using oidc-token the --scope flag can be used to specify a non
default scope.

List Account Configurations

oidc-add and oidc-gen can print a list of available account configurations with
the -l flag.

List Client Configurations

oidc-add can print a list of available client configurations with the -c flag.

Print decrypted file content

oidc-add can print the decrypted account configuration with the -p flag.
oidc-gen can print decrypted account configuration and client configuration
files with the -p flag.

Colored Output

important output is colored

Dynamic Registration

When using dynamic client registration the user can now provide an access token
for authorization at the registration endpoint. This is needed if the endpoint
is not public but protected.

API

C-API

The function getAccessToken has an additional parameter scope. It can be used to
pass a space delimited list of scope values. To use the default scope values
pass NULL.

IPC-API

When performing a token request the field min_valid_period is now optional
instead of required. The default value is 0.

When performing a token request the new optional field scope can be used
to provide a space delimited list of scope values.

Bugfixes

• fixed a number of bugs

oidc-agent 1.1.1

Adds support for debian packages.
Updates Documentation.

oidc-agent 1.1.0

Features

• Dynamic registration (oidc-gen -r) is now the default option for oidc-gen. If a user does not want to use dynamic client registration oidc-gen -m can be used.

API

• Provider configurations are renamed to account configurations. This effects the API in fields like account_list

Bugfixes

• fixes agent's response when it could not get a refresh token. It was success; changed now to failure.

oidc-agent 1.0.5

Features

• Adds the -c flag for oidc-agent. It will skip the daemonizing.

IPC-API

• The provider list is now returned as JSON Array of Strings.
• Changed the socket type from SOCK_STREAM to SOCK_SEQPACKET

Documentation

• Adds description for ipc responses.

oidc-agent 1.0.4

Bugfixes:

• fixes bug where oidc-agent would crash if it receives nonjson message

Docu:

• more precise instruction for dynmaic registration
• updates info about access token validity time

oidc-agent 1.0.3

bugfixes:

• fixed a SIGSEGV
• fixed bug that client config file was not saved
• fixed that the encrypted client config file could not be used by oidc-gen -f

oidc-agent 1.0.0

First release of oidc-agent, including oidc-gen, oidc-add, oidc-token and a client api.