Home

MITREid Connect is a reference implementati4on of the OpenID Connect protocol server and client, built on the Java, Spring, and Spring Security platforms. Java API documentation and a technical overview for the current stable version (generated by the Maven Site plugin) is always available at http://mitreid-connect.github.com/.

The current stable release is 1.2.3. Development of this series is currently tracked on the master branch. To upgrade from the legacy 1.0 or 1.1 series, see instructions at Upgrading to 1.2.

The current legacy release is 1.1.19. Development of this is currently tracked on the 1.1.x branch. The 1.0 and 0.9 release series are no longer supported and upgrade is strongly recommended.

Project Information

Development

• Maven Artifacts, a listing of our published Maven artifacts
• Build Instructions, how to build this project using Maven
• Maven Overlay, the recommended way to build and deploy a custom server
• Supported Features, a list of current and planned features implemented in MITREid Connect

Clients

• Client Filter Configuration, how to configure the MITREid Connect Client-side filter
• Token Introspecting Client Filter, uses Token Introspection to configure a client that can accept tokens from a remote authorization server

Servers

• Server Configuration, how to configure the MITREid Connect server
• Server API, RESTful API for managing clients, scopes, whitelists, blacklists, approvals, and tokens

Related Github projects

There are several related projects under the MITREid Connect umbrella, including:

• simple-web-app A simple application that shows how to integrate the client filters in a Spring Security application.
• example-openid-connect-overlay A simple server that shows how to build an overlay of the server for custom deployments.
• account-chooser A JavaScript and HTML5 application that makes it easy for users to select between multiple issuers.
• json-web-key-generator A Java application that generates public and private keys in the JSON Web Key format, used by both the server and client components. It is important for real deployments to have their own key.