Upcoming Migration: All OAuth2 Clients Moving to the Developer Portal

This announcement is for accounts with OAuth2 clients in the admin portal. If all your OAuth2 clients are in the dev portal (https://lucid.app/developer#/packages), then you don’t have to worry about this message.

Within the next few months, we’re moving all OAuth2 clients from the admin portal into the dev portal, where they’ll be given a new home in automatically created packages. All migrated OAuth2 clients will keep the same clientId, secret, redirect URIs, and embed domains.

These automatic actions will make these changes as seamless as possible:

The new package owner will default to the account owner. Admins with previous access will be added as code editors. The account owner can then manage and give package ownership to someone else on the account. After migration, new admins will need to be manually added to packages in order to manage them.

If a client wasn’t published in the admin portal, it will be marked as privately published after being moved to the dev portal. This will maintain the same distribution and access as before.

If a client was published in the admin portal, then the package will receive a marketplace listing that is tagged as hidden. This is because the dev portal requires a marketplace listing to be published. If you would like to publish a marketplace listing, first update the listing in the dev portal. Then contact our team at support@lucid.co to request that the marketplace listing be made visible.

What you might need to do:

If you need to manage your clients in the dev portal, make sure developer tools are enabled first. For an end user to access the dev portal, they need to enable a user setting (https://lucid.app/user#/settings) > Developer Settings > check Enable Developer tools is enabled.

If your account owner doesn’t manage your clients, they need to assign the ownership package role to a different user on the account after the migration.

Thanks for your patience!

Page 1 / 1

Sorry if this is a dumb question - as an admin who is not a dev, how can I identify clients (if any) that need to be migrated?

@tstone Not a dumb question! You can view this in your Lucid Admin Panel:

Account Admins may navigate to Admin Panel > App Integration > General > Custom OAuth apps > Settings to locate account-level scoped OAuth2 clients before the migration.
If you see any OAuth2 apps listed there, those are the ones that will be automatically moved to the Developer Portal. Access to the Developer Portal for admins can be enabled at the individual account settings-level or assigned from the Admin panel > Users page (details in our Help Center).

If that section in your Admin Panel is empty, your account doesn’t have any clients to migrate, and you don’t need to do anything.

The main things to note here are:

Where admins may find clients in the UI is changing.
Access to these apps are now handled by invitation rather than just visible to admins visiting the Admin Panel. Admins may invite non-lucid admins to manage these apps now and future admins will not be auto added. This allows for more granular permission control of individuals that manage the OAuth2 clients.

Thanks for asking and happy to answer any other questions you have!

Upcoming Migration: All OAuth2 Clients Moving to the Developer Portal

Thanks @Richard Udell , very helpful! I see just one listed there. I can see a creation date, but no idea who originally created it. What’s the best way to determine who created this originally/who is using it?

Hey @tstone , we do not save who created legacy oauth2 clients. Any of the admins on your lucid accounts at that time could have created it.

If the client is listed as public, then it could be used by users outside of your lucid account. If the client doesn’t have a public tag, then only your lucid account’s users could have used it.

@Richard Udell Just to clarify - so the account admin need to have developer role to access the clients after the migration?

@Ragulan That’s correct! You can find more details in our Help Center article, Developer Tools in Lucid.

Note: Account owners have the developer role by default. However, for security, account admin don’t have the developer role by default and cannot assign it to themselves.

After the migration, existing client admins will be added as code editors on the new Developer Portal package. The account owner will be the initial package owner and can transfer ownership or add other developers as needed. Any new admins added later will need to be manually added to the package by the owner.

Great. Thanks @Richard Udell 🙂

Create an account in the community

Log in to the community

Scanning file for viruses.

This file cannot be downloaded