Can you provide a detailed list of the steps you've taken to see this error? This will help us try to perform a recreate.

Please also include the application you are attempting to use to enable this 2FA method.

As of version 1.29.0, we've added a lot more SAML debugging. I'd be interested to know if anyone else runs into this issue and if the extra debugging helps resolve the issue more quickly.

Cheers!
Dan

@dtokarz1

Great! There is also some of this functionality built into FusionAuth that you could explore as well under Tenants > Registration > Email verification settings

Screen Shot 2021-08-03 at 1.42.38 PM.png

Thanks,
Josh

@renu-rauthan90

Thanks for the report! If this is a bug, I would encourage you to fill out a bug report below with additional details.

https://github.com/FusionAuth/fusionauth-issues/issues/new/choose

Thanks
Josh

Hi @casper!

Welcome to the community. This is working as designed. The import API is currently designed to only write new records to the database and not check if the record is already duplicated. This is partly for performance reasons. It maybe be possible to write a script to check existing records, and then only import "new" users based on that feedback, but we do not have any current documented cases of this.

There is an option to get additional information about what is failing on your import.
https://fusionauth.io/docs/v1/tech/apis/users/#import-users

validateDbConstraints [Boolean] OPTIONAL Defaults to false Set this value to true in order to perform additional validation of the request. The import request is intended to be used to populate the initial set of users, this means FusionAuth does not expect to find duplicate users in the database. If a duplicate is encountered a 500 will be returned without this additional validation. If you intend to use this API with existing users in FusionAuth set this value to true to request additional validation be performed on the input request and a 400 response will be returned with JSON body indicating the duplicate values encountered. Setting this value to true will dramatically decrease the performance of this request. If importing large numbers of users in a single request you may need to increase request timeouts to ensure this request does not timeout before it has completed.

I hope this helps,
Josh

With self-hosted FusionAuth, you are downloading the software, starting up a server (VM in the cloud, in your data center, wherever) and running it yourself. You are responsible for monitoring, backups and everything else to keep your FusionAuth instance available to your customers.

With all the cloud options, we run FusionAuth for you. Each level of cloud has a different set of constraints, as outlined in the pricing links (click on the ? for more details), but in general we take care of operating FusionAuth for you. You still control the upgrade cycle, but much of the other maintenance is handled by us.

@spacho

I don't see an open issue. Feel free to log one below!

https://github.com/FusionAuth/fusionauth-issues/issues/new/choose

Thanks,
Josh

@hamburg-developer

Can you elaborate a bit more about what you are looking for functionality-wise? More context may help to address your question.

Thanks,
Josh

@aartiyadavpersonal

Please be mindful of our posting guidelines, as I do believe this question would be better suited for a computer science special interest forum - there is much variability to consider when making career choices. This conversation is a worthy conversation to have, but may not be related to FusionAuth directly.

Thanks,
Josh

https://fusionauth.io/community/forum/topic/1000/code-of-conduct

BE CLEAR AND STAY ON TOPIC
Communicating with strangers on the Internet can be awkward. It's hard to convey or read tone, and sarcasm is frequently misunderstood. Try to use clear language, and think about how it will be received by the other person.

This applies to sharing links, as well. Any links shared in the Community Forum should be shared with the intent of providing relevant and appropriate information. Links should not be posted to simply drive traffic or attention to a site. Links should always be accompanied by a full explanation of the content and purpose of the link. Posting links, especially unsolicited ones, without relevant and valuable context can come across as advertising or serving even more malicious purposes.

Additionally, the FusionAuth Community Forum is for collaboration, sharing ideas, and helping each other get stuff done. Off-topic comments are a distraction (sometimes welcome, but usually not) from getting work done and being productive. Staying on topic helps produce positive and productive discussions.

SHARE MINDFULLY
When asking others to give you feedback or collaborate on a project, only share valuable and relevant resources to provide context. Don't post links that don't add value to the Topic, and don't post unsolicited links to your own projects or sites on other user's threads.

Additionally, don't share sensitive information. This includes your own email address. We don't allow the sharing of such information in this Community Forum, as it can create security and privacy risks for the poster, as well as other users. If you'd like to invite other Forum members to collaborate on a project or work with you, share a link to the repository in which the project you are working on exists. By sharing the link to your project repo - with some information on what your project is and what kind of help or feedback you're looking for - you can invite others to collaborate with you via issues or pull requests without having to share your private information. You can also add others as outside collaborators on your project repo to give them special permissions to help you develop your project.

No. But the user.bulk.create would. See https://fusionauth.io/docs/v1/tech/events-webhooks/events/#user-bulk-create for more details.

@dtokarz1

Interesting fix. I will have to consider why your solution worked. In the end, glad that you were able to get it working!

Thanks,
Josh

Thanks @dtokarz1

I agree; this would be a nice feature to implement for edge cases.

Thanks,
Josh

It may be that you have set up your system to remove unverified users after a certain period of time.

To modify this setting, navigate to Tenants > Edit Your Tenant > Email then to the Email verification settings section.

In this section, you can change your email verification requirements and durations.

Generally speaking, the provisioning depends greatly on the infrastructure being requested as well as the current demands placed on the underlying cloud infrastructure provider.

For smaller deployments, you can expect a 5 to 10 minute timeline. For a setup more aligned with a high-volume system with large CPU and database capacities, you can expect a provisioning time of 20 to 45 minutes.

@aaron

Too add to what Akira mentioned, please keep in mind that advanced registration forms are a paid feature (developer plan or higher) within FusionAuth. Within this feature set, you can use regex commands and add your own custom validation as shown below.

ba3d6675-f745-4ace-9ce5-2c633c2a5f52-image.png

Additionally, under tenants > password there are a number of custom password rules that you can set as well.

In addition to the tenant, there are also some password rules that you can configure on the application level under applications > registration > self-service registration > enabled > type: basic . Here is where you will find a confirm password toggle as well.

Finally, the above applies to a POST event. Meaning the form has to be submitted before feedback is displayed to the user indicating that they failed validation.

There are some Github issues that we are tracking for more realtime validation like events as well. If you have a unique use case - feel free to log an issue as well.

https://github.com/FusionAuth/fusionauth-issues/issues/1223

Thanks
Josh

If they are on community there is no license. So from community to any paid edition you’d have to enter the license key.

Other than that, no change to the config is required or expected.

If you are changing from a paid edition to community edition, log in to your account at https://account.fusionauth.io and modify the edition. This will render the existing license key inactive.

@rvogelgsang to follow on with what @akira wrote, you can also just set the password to a random unknown string too.