Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

User migrator: oauth applications

See original GitHub issue

For each user:

Migrate client_applications
Migrate oauth_tokens
Migrate redis tokens: $api_credentials -> rails:oauth_access_tokens:*. This is done in the after_create hook of saving oauth_tokens with the Sequel model, so we could use that.

After that, fix for existing users.

Issue Analytics

State:
Created 5 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

javitoninocommented, Jun 18, 2018

Ran the migration for existing users. I’ll submit a small PR later for the retrocompatibility thingy.

0reactions

AleGoikocommented, Jun 15, 2018

:ohno: I tested that client apps and tokens were migrated but not a regular case 💔

Top Results From Across the Web

Migration: OAuth 1.0a to OAuth 2.0

Use this endpoint to migrate users of your application from OAuth 1.0a authentication to OAuth 2.0 authentication to access the v1 and v2...

How to migrate your legacy user data to a centralized auth ...

How can you safely and easily migrate your user's data from a legacy user datastore to a centralized auth system?

Migrating from Google Sign-In | Authentication

User sign-in no longer requires you to understand or work with OAuth2 authorization codes, access tokens, or refresh tokens. Instead a JSON Web ......

Migrating users from an existing app | Identity Platform ...

You can import users to all of the providers Identity Platform supports, including OAuth, SAML, and OIDC. Up to 1000 users can be...

OAuth 2.0 requirements and migration - DocuSign Developers

OAuth 2.0 requirements and migration · Currently, for non-partner REST API apps, only REST apps that use OAuth 2.0 are able to go-live....