OAuth 2 / OpenID Connect Client API for JavaScript Runtimes
OpenID 1.1/2.0 library for Node.js
Low-Level OAuth 2 / OpenID Connect Client API for JavaScript Runtimes
oidc-token-hash validates (and generates) ID Token `_hash` claims such as `at_hash` or `c_hash`
Express middleware to protect web applications using OpenID Connect.
A general purpose OAuth client.
Angular Lib for OpenID Connect & OAuth2
OAuth 2.0 Authorization Server implementation for Node.js with OpenID Connect
OpenID authentication strategy for Passport.
Extensions to support OpenID Connect with OAuth2orize.
Terminal and Web console for Kubernetes
OpenID Connect (OIDC) & OAuth2 client library
OpenID Connect authentication strategy for Passport.
CDK constructs to use OpenID Connect for authenticating your Github Action workflow with AWS IAM
Auth0 platform authentication strategy for Passport.js
<h1 align="center" ><b>OpenID for Verifiable Credentials - OAuth2 Utils</b></h1>
OAuth 2.0 Authorization Server implementation for Node.js with OpenID Connect
<h1 align="center" ><b>OpenID for Verifiable Credentials - OAuth2</b></h1>
AWS SDK for JavaScript Sso Oidc Client for Node.js, Browser and React Native
<h1 align="center" ><b>OpenID for Verifiable Credentials - OpenID4VCI</b></h1>
<h1 align="center" ><b>OpenID for Verifiable Presentations - OpenID4VP</b></h1>
OpenID authentication strategy for Passport.
Integration for OpenId/AppAuth-JS into Ionic
Fetch utils for JWKS keys
openid-examples demo collection.
OpenID Connect & Discovery client library using async / await.
A store is required by an OpenID server and optionally by the consumer to store associations, nonces, and auth key information across requests and processes. If rails is distributed across several machines, they must must all have access to the same OpenID store data, so the FilesystemStore won't do. The code here is copied from the openid-ruby library examples. All I did was move some things around, add a namespace and package it all up as a rails engine/plugin, with some conveniences, for use with Rails 3.
MySpaceID lets your users log on using their MySpace account info, after which their MySpaceID data becomes available; that is, your web servers will be able to communicate with our web servers and request user data. This SDK project contains examples of the base API code necessary to make signed requests against the MySpaceID REST API. To use the MySpaceID API, you first need to register on the MySpace Developer Site, create an app, and obtain a consumer key and secret. Information about these procedures, and about MySpaceID in general, is available at the MySpaceID Developer Wiki: http://wiki.developer.myspace.com/index.php?title=Category:MySpaceID The MySpaceID Ruby SDK enables you to work with MySpace data using the OpenStack (OpenID, OAuth etc) and the MySpace REST APIs via easy-to-use high level interfaces. The best way to implement your own application is to take an existing sample and customize it. Working Examples in this SDK: * OAuth - make signed requests * OpenID + OAuth Hybrid - delegated login, and making signed requests Documentation * Ruby SDK Documentation Summary: samples/rails/README * Ruby SDK - API Documentation: http://myspaceid-ruby-sdk.googlecode.com/svn/trunk/doc/index.html