@alex-nebula99 This video might be helpful. You have to turn on webhooks in two places.

@gabriel-rod-cas-10 The way I read the migrate option is that, once migrated, future authentications will use FusionAuth and not the connector. The user will still be created in any case.

Depending on what you are trying to accomplish and why, there can be some other ways to work around. We do have APIs and other extensibility points that would allow you to delete a user and that sort of thing.

@daniel-b Can you please give us a little more information about your setup? I.E. The configuration, the version of FusionAuth you are using, the version of MySQL etc?

According to the docs FusionAuth supports MySQL 8.0 or newer. More specifically:

MariaDB and Percona may work, however these variants are not actively tested against by FusionAuth.

See MariaDB known issues on our GitHub issues.

@ronn316 Thank you so much for sharing with the community and I'm glad you got it working for you!

@ronn316 Awesome glad to see you got it working. I'm sure there is a way to use a dns name, but like I mentioned before, someone with a little more docker experience would have to help us out here. Thanks for working this through and sharing with the community.

@mark-robustelli Sorry for the late response, I just saw this. I'm using 1.48.1 and yes, FusionAuth is the IdP. Thanks for the quick response!

@panpsonis , I don't know of anyone that has gone from the version that you are on to the latest. That doesn't mean you can't, you will just need to test. Here are some recommendations from the documentation if you haven't seen it yet.

https://fusionauth.io/docs/operate/deploy/upgrade#skipping-versions

@ronn316 Awesome! Thanks for sharing.

@j-smutek

Hi, after a long bit of working on this issue.
I am quite certain that it is caused by setting a valid certificate in the configuration.
It happens when you configure it directly in the fusionauth.properties file ssl. Everything appears to work, then you find out you cannot create or edit tenants, and other areas do not work randomly. I would just get at no response in the browser and then this buffer overflow in your logs.. I struggled for quite some time with this. Just writing here so if someone else comes to this point.. Just stop and install a reverse proxy problem solved.

I also think honestly fusionauth's quick guide should include setup with caddy and/or nginx with ssl certs. Really I think it would be best to remove ssl setings and force users to setup a reverse proxy as it is simple to do. But I see that you maybe want flexibility here. I have done this now with Caddy and it works flawlessly.

Thanks again for a great product though and great community support.
Authfusion is by far the easiest alternative to Indentity Server for .net and probably the easiest auth server I found.

@theraloss said in Prevent sending "locale" query string to the redirect URL?:

locale=en_US

When you query the user, does anything show up in the preferred languages? Also, are you using the FusionAuth hosted login pages?

Have you used a network monitor to see if the the local is put into the query string by FusionAuth or the IdP?

It is possible to configure in this way.
You can customize the forgot password email template to display the generated changePasswordId rather than using it as part of the URL.

Two pages will need to be customized for the theme:

Forgot password sent - update this to forward the user to the “Change password form” page. One option to perform this redirect is to use a meta refresh tag Change password form - the default template uses a hidden element to submit the changePasswordId. You can use another form field that the user fills out to submit the code.

FusionAuth hosted pages will require the verification code and updated password to be submitted on the Change Password form page.
Please also note the potential security implications of shortening the verification code to 4 digits instead of the default 32 encoded bytes.

@maysilees I don't believe we have a setting for this but you could add your own lambda, which you would then have to do an API call to check for the number of users.

https://fusionauth.io/docs/extend/code/lambdas/

https://fusionauth.io/docs/extend/code/lambdas/self-service-registration#self-service-registration-validation-lambda

To check the number of users in a specific tenant using the FusionAuth API, you can use the "Search for Users" API endpoint. This endpoint allows you to search for users within a tenant and can be used to count the number of users. You would need to set the tenantId in the search criteria to scope the search to a specific tenant.
Here is an example of how you might use the API to search for all users within a tenant and count them:

FusionAuthClient client = new FusionAuthClient("your-api-key", "http://localhost:9011"); ClientResponse<UserSearchResponse, Errors> response = client.searchUsersByQueryString("tenantId:your-tenant-id"); if (response.wasSuccessful()) { // The total number of users in the tenant can be retrieved from the total field in the response int totalUsersInTenant = response.successResponse.total; System.out.println("Total users in tenant: " + totalUsersInTenant); } else { // Handle error response }

Please replace your-api-key with your actual API key and your-tenant-id with the ID of the tenant you want to search. The searchUsersByQueryString method is used to perform the search, and the total field in the successful response will give you the count of users in the specified tenant.
Note that the above code is a conceptual example based on the information provided in the extracts. The actual implementation may vary depending on the version of the FusionAuth client library you are using and the specific details of your application.
For more details on the "Search for Users" API, you can refer to the FusionAuth API documentation, which would typically be found at the following link: Search for Users API. However, please note that this link was not provided in the extracts, so you should consult the official FusionAuth documentation for the most accurate and up-to-date information.

FusionAuth does allow for extensive customization of themes, which may be used to ensure WCAG compliance.

To create and manage themes, you can navigate to Customizations -> Themes in the FusionAuth UI or API. More here: https://fusionauth.io/docs/customize/look-and-feel/

Themes are written in FreeMarker, which provides a rich template language to customize pages and helpers to suit your needs. This could include adding accessibility features to meet WCAG standards.
If you need to manage complex configurations such as themes programmatically, you can use the FusionAuth CLI.

If you're looking to ensure that your custom theme meets WCAG requirements, you might need to consult WCAG guidelines and ensure that your theme modifications align with those standards. This could involve adding appropriate ARIA labels, ensuring sufficient color contrast, providing keyboard navigation, and more.

@theuniversalvillagers

Hmmm. I'm not sure I understand your question. Can you walk me through what you are trying to do, step by step?

Hi @jacob-fisher,

So you are saying that you have this situation:

In FusionAuth, a user user@example.com

In salesforce, a user user@example.com.

You configure salesforce to use FusionAuth as the source of identity, so there's a Login with FusionAuth button on salesforce.

When you try to log into salesforce in an incognito window, you see a new saleforce user with the email address user@example.com created (so now there are two)?

What are the two user ids? It's possible there is a mismatch and you might need to adjust the apex code.

Is that correct?

@mark-robustelli Thank you. It is an interesting workaround. I think if we apply encryption on top of the generated string value, it will not disclose user's login.

@altear147 I encountered this behavior today when I tried to update the username for a user:

await getFusionAuthClient(tenantId).updateUser(userId, { user: { username, }, });

To my surprise (but probably only the lack of knowledge), this set theusername of the user as specified but also deleted the email just as you described.

I was thinking, okay, let's move on and don't touch username and specify firstName as the only key for the update:

await getFusionAuthClient(tenantId).updateUser(userId, { user: { firstName, }, });

but then I received this error:
16e0e85b-affe-4d49-be46-bf5a05f5d811-image.png

Which I also didn't expect, since I assumed the userId uniquely identifies a user and I don't have to supply more fields to help FusionAuth identify it.

After supplying the exact same things as you did:

await getFusionAuthClient(tenantId).updateUser(userId, { user: { email: email as string, firstName: firstName as string, lastName: lastName as string, mobilePhone: mobilePhone as string, }, });

my user object is getting updated. To clarify, the email input is disabled on my form, and users can only enter first name, last name, and mobile phone.

You can find the complete code here: https://github.com/akoskm/saas/blob/main/app/routes/team_.%24userId.edit.tsx

Hope this helps.

@dan I opened the request. Thanks!

@dan Hello, reaching out to know if this still the same, ie no way to know whether an user has a password or not?