The only two grants that are relevant to an interactive flow are the authorization grant, and the implicit grant.

I don’t recommend you use the implicit grant at all, so that leaves only the authorization grant.

If the authorization grant is happening, response_type will be code.

If the authorization grant is occurring due to a device grant, the user_code variable will be set.

Yes, it's on the roadmap: https://github.com/FusionAuth/fusionauth-issues/issues/769

This is something we want to solve. Currently the best solution is to use branch logic or stylesheets in the templates based upon the client_id which will be unique for each application.

Another alternative is to have separate tenants for each application (after all, you can have as many tenants as you want) but that may cause issues because the user accounts in different tenants will be disconnected.

You can put whatever you want in the theme pages, but it's a good idea to keep them lean so the user has a quick login experience. After all, most folks don't care about auth except when it doesn't work!

You can optionally pass info in the state parameter, that will come back to the caller. This can be encoded JSON, as long as it is url safe. You will want to make sure that you don't put too much stuff in there, as there are URL length limits for browsers (though I learned that chrome has a URL size limit of 2MB!). Here's an example of using the state parameter for application state.

Or if you have different applications and redirect URLs, then just gathering metrics on the URLs may give you insight into who is using login, and from where.

Sort of depends upon what type of analytics you need.

This link is probably what you are looking for:

https://fusionauth.io/docs/v1/tech/themes/#handling-failures

In order to use a custom font within a publicly accessible FusionAuth template for a hosted deployment, pull the font from a CDN or other server hosting the font.

FusionAuth doesn't have any persistent storage for custom theme assets. You can use any font you like as long as it can be included via a tag.

No, we don’t provide any persistent store for assets like images, CSS files or favicons.

You’ll need to just use accessible URLs in your theme for those assets.

Hiya,

The issue is that the identityProviders map needs to be populated for that login script to work, and the class behind this page doesn't provide that map. So for now I don't see a way to do this.

There is an open github issue to allow identity providers to be displayed on the registration page. I'd suggest adding your use case to that issue: https://github.com/FusionAuth/fusionauth-issues/issues/554 and I'm happy to rename it to something more general. Alternatively you can file a new issue if you feel the use case is distinct enough.

Themes are mapped to tenants. Per https://fusionauth.io/docs/v1/tech/apis/themes

Themes are configured per Tenant.