I totally forgot to add the register the user manually to the FusionAuth application. It is working now, thank you!

What's a good way to generate a URL that would take a user directly to the registration page (bypassing the login page) and with a redirect URL? It's an ASP .NET Core app. Do I need to use an API or is there a more "direct" way?

I feel like this has been asked and answered before but my search fu failed me.

Ahh! So leave out encryptionScheme, factor, and salt and set password to a 32 bytes random password. Makes sense. Thank you!

That makes sense. Thanks @dan!

That makes sense. Thanks @dan!

Is there an "automatic" way to register a user to a different application, say, a mobile app, when they register for, say, a web app? Or do we have to do that at the application level using an API?

Ahh! So leave out encryptionScheme, factor, and salt and set password to a 32 bytes random password. Makes sense. Thank you!

Out of curiosity, "then FusionAuth will hash the password inline before it stores the value". What determines a non-hashed password? The absence of salt?

@dan It does! We are trying it out today to see if it works or not. I'll report back. Thank you so much for jumping on it and coming up with a solution.

What's a good way to generate a URL that would take a user directly to the registration page (bypassing the login page) and with a redirect URL? It's an ASP .NET Core app. Do I need to use an API or is there a more "direct" way?

I feel like this has been asked and answered before but my search fu failed me.

I totally forgot to add the register the user manually to the FusionAuth application. It is working now, thank you!

Is it possible to have multiple admins on a single FusionAuth instance? I created an "admin" group with all the permissions selected and then added a new user to this group. When I tried to login using this new user, I get this message

Your account does not have permissions to access the FusionAuth Admin Interface. Please contact your system administrator.

That's exactly what I ended up using (by adding it as a custom claim in a lambda function)

function populate(jwt, user, registration) {
  jwt.provider = Object.keys(registration.tokens)[0];
}

. The only problem is that I don't seem to be able to pass all the tokens and then "map" it out in the backend. Also, I think I already know the answer to this and this may sound dumb, but how can you have multiple tokens? A user with multiple providers? If so, how are they consolidated and combined?

Lastly, it would have been nice if user.registrations had a providers field.