No more passport, just use simple REST API for OAuth2.
n8n node for bitrix rest api
OAuth 2.0 authentication strategy for Passport.
TypeScript definitions for passport-oauth2
Node.js client for OAuth2
Complete, framework-agnostic, compliant and well tested module for implementing an OAuth2 Server in node.js
Allow parsing of object rest/spread
Compile object rest and spread to ES5
TypeScript definitions for simple-oauth2
Google (OAuth 2.0) authentication strategy for Passport.
Support for OAuth 2(.1) and OpenId Connect (OIDC) in Angular
Google OAuth2 using Google Identity Services for React 🚀
TypeScript definitions for passport-google-oauth20
HTTP/REST CLI Client for *.http files
Complete, framework-agnostic, compliant and well tested module for implementing an OAuth2 Server in node.js
OAuth2 client for browsers and Node.js. Tiny footprint, PKCE support
Octokit plugin adding one method for all of api.github.com REST API endpoints
Authentication middleware for Express.js that validates JWT bearer access tokens.
oauth2
TypeScript definitions for oauth2-server
Perform login using oauth2 protocol
Straight-forward execution of OAuth 2.0 flows and authenticated API requests
Workaround a Safari bug where rest destructuring with an array literal on the rhs can yield incorrect results
Validate ascii and unicode values.
This is the simple REST client for Google OAuth2 API V2. Simple REST clients are Ruby client libraries that provide access to Google services via their HTTP REST API endpoints. These libraries are generated and updated automatically based on the discovery documents published by the service, and they handle most concerns such as authentication, pagination, retry, timeouts, and logging. You can use this client to access the Google OAuth2 API, but note that some services may provide a separate modern client that is easier to use.
MailUp OAuth2 Strategy for OmniAuth 1.0.
Force.com/Database.com RESTful API OAuth2 Strategy for OmniAuth
Access the Tipalti REST API via OAuth2.
Consumes the Facebook OAuth2 Graph Rest API
Ruby Client for the Assembla. Performs REST based HTTP calls to api.assembla.com using OAuth2
O2 Labs has exposed the power of #blue to developers via a simple REST & JSON based API, combined with oAuth2 to developers who can create new ways for users to manage their texts and add combine the ubiquity of SMS with their applications, users simply grant an application access to their messages stream or just certain messages.
A clean, test-driven Ruby SDK for MangoApps APIs with OAuth2/OpenID Connect support. Provides modular, easy-to-use methods for interacting with MangoApps REST APIs including Learn (courses, categories), Users (profiles), and more. Built with real TDD and comprehensive error handling.
This gem is like the `warden_openid_auth` gem, except that it only provides support for the very last step of the OAuth code flow, i.e. when the resource server / relying party (your Ruby Web app) validates the bearer token. Use this gem if your client-side Web (or mobile) app will be taking care of the rest of the OAuth2 motions, such as redirecting (or opening a popup window) to the authentication server at login time, managing and refreshing tokens, doing all these unspeakable things with iframes, etc.
This documentation describes your available CheckAPI REST services: Get your checkpoints and their details, check the permission of a customer's ID, take a look at your checkpoint's history - everything a checkpoint needs can be found here in one place. Please look at the descriptions in each service below. <div id="authorize-information-wrap"><h1>Authorize</h1><p>You can use this automated authentication to try out your activated methods - just click „Authorize“, enter CardAPI credentials and have a try! You received the CardAPI username and password via e-mail – credentials are different from your developer-portal credentials. Authentication is based on OAUTH2 (implicit grant flow) and needs to be implemented and called prior to using any API method. <b>CLIENT_ID</b><br>The client ID is pre-filled automatically according to the chosen application. You can find your available client IDs in the "Applications" - Area. <b>GRANT_TYPE</b><br>With grant_type=password you get an access-token and a refresh-token for your request. The received access token can be used for 10 minutes, there are two ways to renew it. Either you can send the same request again or you can use the grant_type=refresh_token. The refresh token needs to be used every 30 minutes and can provide new access tokens for 10 hours without using your credentials.</p></div>
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.