OpenCCT, OpenID Connect SSO Java client library

Registering the target application within the authentication server

The registration operation consists of the providing of the requested parameters, mainly:

The type of the application, needs to be «web type».
A redirect URL that allows the server to respond to OpenCCT requests. Use: <APPLICATION_URL>/authcallback.
The preferred security algorithm must be RS256. Allowed by all servers and usually default taken.
The server to server authentication method must be Client secret basic (id + password). Allowed by all servers and sufficient for most use cases.

Other optional parameters can be provided to improve the end user information. These settings may include URLs to access information documentation, an application logo or other. The used server documentation should be revieweded for further details. At the end of the registration, the authentication server must provide an identifier and a password which make it possible to secure the communications. This provided data corresponds, respectively, to the client_id and client_secret parameters of the OpenID Connect specifications.

Setting

The following configuration example is using the Google authentication server.

<filter>
  <filter-name>auth-filter</filter-name>
  <filter-class>net.meddeb.oauth.opencct.AuthFilter</filter-class>
  <init-param>
   <param-name>login-endpoint</param-name>
   <param-value>https://accounts.google.com/o/oauth2/v2/auth</param-value>
  </init-param>
  <init-param>
   <param-name>token-endpoint</param-name>
   <param-value>https://www.googleapis.com/oauth2/v4/token</param-value>
  </init-param>
  <init-param>
   <param-name>oauth-id</param-name>
   <param-value>CLIENT_ID_PROVIDED_BY_GOOGLE_REGISTRATION</param-value>
  </init-param>
  <init-param>
   <param-name>oauth-secret</param-name>
   <param-value>CLIENT_SECRET_PROVIDED_BY_GOOGLE_REGISTRATION</param-value>
  </init-param>
</filter>