Getting Started

Register your experience

Before using FutureverseProvider container you will need to register an OAuth2 client with the Futureverse Identity Provider using the Manage Clients Console:

You will need to provide two arguments:

  • Client Name: The name of your application (e.g. futureverse-experience-demo).

    • Use only alphanumeric characters, - and _.

    • This does not have to be unique, you can re-register with the same name to receive a fresh set of credentials.

  • Redirect URLs: Specify your application's URL(s) to redirect to after a successful login. Follow these guidelines:

    • Include the protocol in the URL (use http for development and https for production).

    • Separate multiple URLs using semicolon.

    http://localhost:3000/home; http://localhost:3000/login; https://*-demo.preview.com/home; https://*-demo[.preview.com](http://futureverse.vercel.com/)/home; https://futureverse-experience-demo.staging.com/home;

    This example registers different redirect URLs for various environments:

    • http://localhost:3000/home for local development.

    • https://*-demo.preview.com/home for dynamic deployments with wildcarded preview URLs.

    • https://futureverse-experience-demo.staging.com/home for the staging environment.

Note: Wildcards in Redirect URLs are only available when registering using the Development portal listed above. When registering your app for production you need to provide full Redirect URLs.

Upon successful registration, you will be presented with a Client ID, Name, and an Access Token. Make sure to save these. You will need the Client ID and the Redirect URL in your application to configure the FutureverseProvider. Treat them as any other secrets in your application (so do not commit them with your code!).

Client Name and Access Token are used to view and edit this registration, they are not required in the codebase.

Last updated

Feedback

Docs

© 2023 -> ♾️