You'll receive an error in both scenarios.

If you are using the web interface, you'll get a red message saying "Already exists".

forum-edit-user-email.png

And if you are trying to use the Update User API endpoint, you'll receive a HTTP 400 Bad Request error:

forum-edit-user-email-api.png

Even though we don't have specific SDKs for mobile apps, we do have a Flutter quickstart which uses our Dart client library.

If you want to develop natively, we recommend using AppAuth, which has iOS and Android SDKs and is maintained by the OpenId Foundation:

https://github.com/openid/AppAuth-iOS https://github.com/openid/AppAuth-Android

There's also a FusionAuth Swift Client maintained by the community.

Hi there!

Please make sure that you have selected that Lambda in your Application by navigating to its edit page, going to the JWT tab and choosing it on Access Token populate lambda.

For instance, my (extremely simple) function looks like:

function populate(jwt, user, registration) { jwt.customClaim = 'gotcha'; console.debug(JSON.stringify(user)); }

And I received the following access token with that customClaim at the end:

235241bf-3086-4565-a424-a14398bdcafd-image.png

Sorry, after further testing i noticed that if the registration fields are disabled, then the registration process is ignoring them. I had to emulate the disable with "readonly" and some style:

<script type="text/javascript"> window.onload = function () { const queryString = window.location.search; const urlParams = new URLSearchParams(queryString); if (urlParams.has('user.email')) { document.getElementById("email").readOnly = true; document.getElementById("email").style.backgroundColor = "#1e73be"; document.getElementById("firstName").readOnly = true; document.getElementById("firstName").style.backgroundColor = "#1e73be"; document.getElementById("lastName").readOnly = true; document.getElementById("lastName").style.backgroundColor = "#1e73be"; } }; </script>

@dan The configuration files and logs are inaccessible, assuming you're talking about the ones residing up a directory from /fusionauth-app/.

Thank you for stating the risks of the leakage. The only thing that raised flags here was the default fusionauth.properties file in the template directory had the default database user and password, but those should be, and were, changed when installing.

I will fork and submit a PR later tonight or this week.

Thanks again.

@yves

I'd be interested to see if the same issue occurs on the latest version of FusionAuth. There's 4-5 mentions of Elasticsearch in the release notes between 1.34.0 and 1.45.3, but none of them appear to address what you are seeing.

As mentioned above, also searching directly via id for example fails.

Sorry, I missed that. Are you saying when you search using the ids method (described here under the heading Search for Users by Id) it doesn't find these users? Because that search should go directly to the database and not through ES at all.

It's all a bit suboptimal.

Off topic, but please consider adding your voice to this issue which might help with your schema changes.

@beezerk I'd suggest modifying the theme and adding a link and a meta redirect. I don't think there's any way to specify a redirect.

@dot-realities

Hmmm. It seems like you want to have email verification take place entirely outside of FusionAuth. Is that the case?

If so, you should:

suppress sending any emails to FusionAuth, which will typically will verify emails (you can turn that off by setting tenant.emailConfiguration.implicitEmailVerificationAllowed to false) send emails yourself, using whatever system you want verify the user's email directly, using an API key (search for Administratively).

Does that meet your needs? If not, please provide more information.

No, that's not how it is supposed to work.

3v7vibqk0j3b1.png

This has been fixed in version 1.46.0, which should be released soon.

You can track it at the issue above.

Thanks for reporting, @ndiarmand !

@joaogoncalves Hiya, I don't think that is supported. I'd suggest using two different Application configurations in FusionAuth, though I'm sure that's something you've already considered.

Feel free to file a feature request: https://github.com/FusionAuth/fusionauth-issues/issues/

@troy-squillaci I think you need to set the value of database.root.user.

If that is not set, FusionAuth can't create any tables, which it will try to do if the tables are not set up.

Have you manually bootstrapped your database (that is, run the sql as documented here to create the needed tables)?

Also, I added some documentation to help folks to find this easier: https://github.com/FusionAuth/fusionauth-site/pull/2219

Should be live in a few minutes.

Since the original post is from two years ago, it's important to consider that the technology landscape and integration options may have evolved since then.

@vinicius-campitelli thank you!

@mangeshp16 The original question is over two years old. Since version 1.42, you can enforce MFA at the tenant level (or the application level if you have the enterprise plan). This means that any user who logs in is required to have MFA. If they do not, they are redirected to a page where they can set it up.

There are other ways to accomplish this. You could build your own MFA page which would call the APIs directly. When a user logs in, you can check to see if they have any twoFactor methods available and if they don't, you can send them to this page.