Hi @joshua,

Thank you for your reply! I will reach out to sales@fusionauth.io for additional assistance.

@nicholas-tsaoucis

Glad you figured this out!

Thanks,
Josh
FusionAuth

You should be able to return the two factor JSON as documented in the user response object. Have you tried doing that?

user.twoFactor.methods[x].authenticator.algorithm and others.

@minhngocnguyenduy Glad you found a solution!

@hanumant-sidraya

Do you mean you want to deactivate all users who were authenticating with a given connector? This is not a typical use case, so you'll need to write some code to do this.

If so, then I'd script the removal of the connector and at the same time mark all users associated with that connector as inactive (or you could hard delete them if you want).

The connectorId is not one of the searchable attributes for users, so the easiest way to do this would be to have your custom connector set an attribute on the user.data field, something like user.data.authDataSource = clientXYZ or similar.

Then you could query for all users with that user.data value and deactivate or delete them.

Hope that helps.

Thanks for sharing this! I'm glad you figured it out. I'll add a note to the sample application pointing to this forum post.

Hi both @aj-merts @wernervdwath

If I put this in my browser

http://savant.inversoft.org/com/mysql/mysql-connector-java/8.0.12/mysql-connector-java-8.0.12.jar

or

https://savant.inversoft.org/com/mysql/mysql-connector-java/8.0.12/mysql-connector-java-8.0.12.jar

I am able to download this jar.

Can you confirm this is still an active issue for you? If so, error logs or additional configuration info may be useful in debugging.

Thanks,
Josh

@patrick

Perfect 👌

@ali-sch

It is specified on the Connectors page that all connectors are a paid edition feature, but it should be clear on the pricing page as well.

Sorry about that oversight! We'll update the pricing page.

If you are interested in kicking the tires to see if connectors will solve your problem, please either contact us to chat with a sales rep, who can set you up with a trial, or sign up for a two week trial of developer edition on that pricing page. You'll have to provide a credit card, but can cancel any time in the first two weeks at no charge.

First, ensure your instance meets the requirements outlined here. In particular:

When using the Advanced Threat Detection feature, a minimum of 2GB of heap is required, and 3GB is recommended.

You also need to make sure the instance has outbound network access.

If this doesn't work, please open a support ticket.

@hanumant-sidraya

🎉 🙂

There is no built in support for this, but you may be able to modify your theme to allow for this functionality using javascript.

Here is a relatively simple example online - https://www.w3schools.com/howto/howto_js_toggle_password.asp - that should be helpful.

These are documented in here: https://fusionauth.io/docs/v1/tech/apis/users/#import-users

user.encryptionScheme is the field value to look for.

If you are using a custom password hasher, as outlined here: https://fusionauth.io/docs/v1/tech/plugins/custom-password-hashing/ you want to use the name that was used to bind the hashing class in the plugin module.

Currently the way you would do that is by using the short version in the custom field definition. This will be the programatic value that is persisted. For example:

US DE

Then in your message bundle (managed by the theme), you can translate those values into a more human readable option.

US=UNITED STATES DE=GERMANY

If we do not find a localized key, we will just use the key as the value which would then render as <option value="US">US</option>.

@rwheelerflemming

Please close this. I'm a moron and was using the Key ID instead actually clicking and revealing the Key Value.

Trust me when I say this - We have all been there RE: pebcak. 🙂

Glad you got it figured out!

Thanks,
Josh

@andres-garcia

I might lack a bit of context, but I think that

user is already created on FusionAuth

You do have the option to choose how FusionAuth will look for users on the tenant (more in the documentation). So you might have FusionAuth look for your user in an external LDAP connector, firstly, for instance.

So I was trying to do it that way because I can't provision the service async using the webhooks.

Is this a limitation of your architecture/design or a limitation you are finding within FusionAuth

Thanks,
Josh
FusionAuth

There is a known issue with performance if you are running our intel based Docker image on an M1 or other ARM based system.

We will be pushing out support for M1/ARM shortly..
We have a test image out there if you want to try it - using this one should provide much better performance.
https://hub.docker.com/layers/fusionauth/fusionauth-app/1.32.1_multi/images/sha256-da71d5be2bc849ef9d4e1205508fa34994973d75798a47cab9a8484ee2592ff7?context=explore

is the latest current experimental version. Make sure you choose the arm64 based image.

You can't do this with the hosted login pages, but there is an issue to allow/disallow MFA on an application by application basis: https://github.com/FusionAuth/fusionauth-issues/issues/763

Currently, you can't bypass MFA, but you can do an end run around by using the Login API.

You can start multi factor with a code you provide: https://fusionauth.io/docs/v1/tech/apis/two-factor/#start-multi-factor

Then complete the login process with that known code: https://fusionauth.io/docs/v1/tech/apis/login/#complete-multi-factor-authentication .

@maciej-wisniowski

Glad that you are able to figure it out. I am not sure if that qualifies as a bug, but definitely something to be aware of and might be worth calling out in our documentation.

I believe that you should have email templates after a kickstart (at least the default ones). I can do some more testing to see if that same thing happens to me when I kickstart.

Thanks,
Josh

@shaheem-aziz

Glad that you are enjoying FusionAuth!

The role name is not changeable. To change the name, you would have to remove the role and then re-add with a new name.

This only applies to the role name. The other fields (isDefault, Description, etc), however, are changeable.

Thanks,
Josh