Derniers articles

• OpenID Connect : get access tokens

  3 mai 2019, par B. Degoy

  We are in the case of Authorization Code flow.
  The client application must have an access token to obtain protected data from a resource server. The necessary code is entirely the responsibility of the author of the client application, in response to redirection on the URI of the redirection (…)

• OpenID Connect : Get an authorization for the client application

  3 mai 2019, par B. Degoy

  As part of the Authorization Code Flow, the end-user’s user-agent (usually a web browser) is redirected to the Authorization Endpoint , to allow it to identify itself and grant permissions to the client application. If successful, the user-agent will be redirected to Endpoint Token with an (…)

• Authentication using the OpenID Connect authorization code flow

  3 mai 2019, par B. Degoy

  This section explains how to perform authentication using the Authorization Code Flow.
  The diagram opposite gives a more detailed idea of the continuation of the exchanges between the 3 poles of a authorization flow via a code. Click on the image to enlarge
  The rest of this article is an (…)

• Link a client application to the OAuthSD server

  3 mai 2019, par B. Degoy

  This article is for a developer.
  It describes how to adapt an application to make it an OpenID Connect client and how to register it on OAuth Server byDnC.
  This assumes that the developer or his organization is registered on the server as an Application Administrator.
  The process has two (…)

• Plugin OpenID Connect Client pour SPIP

  26 avril 2019, par B. Degoy

  Un client OIDC pour SPIP. Permet à une application SPIP de proposer l’authentification avec OpenID Connect, à côté de l’authentification classique.
  Les développeurs d’application SPIP pourront renforcer la protection de l’accès aux fonctionnalités réservées et à l’espace privé en limitant (…)