This requires both some frontend (JS) development, but also some changes to the backend system so that we can distinguish a Keplr user from an auth0 (social) user in their user profile.
Ideally, we would have a Regen Identity Provider which maintained the user profile and did any necessary authentication of users as a separate service, providing authorization tokens (a la OAuth 2) to relying party services such as Registry.
This requires both some frontend (JS) development, but also some changes to the backend system so that we can distinguish a Keplr user from an auth0 (social) user in their user profile.
Ideally, we would have a Regen Identity Provider which maintained the user profile and did any necessary authentication of users as a separate service, providing authorization tokens (a la OAuth 2) to relying party services such as Registry.