@dtokarz1 That's great! Glad you figured it out, and thanks for letting us know.

I have no idea about this.

To add on to what @joshua said, you control the upgrade timing and therefore any resulting outages.

We don't share individual customer uptimes, since that is tied to their usage and the level of resources they have chosen for their individual deployment.

@rpy I think this is the issue you are looking for: https://github.com/FusionAuth/fusionauth-issues/issues/1996

This is slated for release 1.43, which should be out in the next month or so (could be sooner, we're trying to get a few more bugfixes in there).

@lambert-torres replied out of band to this forum. This may have been addressed in version 1.38.0 and beyond.

Thanks,
Josh

Thanks for the information keep sharing such informative post keep suggesting such post.

Hi Josh,

Thanks for taking the time to reply. In the scenario outlined I perhaps didn't mention that the users I was expecting the webhook to fire for already existed in FusionAuth prior to Azure AD sign-in. Should I expect the event to trigger in that instance?

Regards
Stefan

@dhait Hmmm. This issue is due to the OAuth2 specification. If we provided a REST endpoint, it wouldn't be OAuth/OIDC.

If you want to fully customize the look and feel of the login and registration experience, but not use the FusionAuth hosted login pages, the recommended solution is to code directly against our REST APIs:

https://fusionauth.io/docs/v1/tech/apis/login

https://fusionauth.io/docs/v1/tech/apis/registrations

Does this solve your problem?

@julien-sarriot What does turning on the debug log do? https://fusionauth.io/docs/v1/tech/admin-guide/troubleshooting#enabling-debugging has instructions on how to do that and where to look after (in the event log).

Please share that info here.

@benji-levens

Hmmm.

Can you please share the code you are using to try to change the user's password? Letting us follow the exact steps might be helpful.

Additionally, 1.32.1 is a year old. You may want to consider upgrading.

@cyril-feraudet I think this post answers your question:

https://fusionauth.io/community/forum/topic/2253/blocking-domains-from-registration

@zradick

Thanks for the question - if you remove the quotes from your args, that may resolve the issue.

- FUSIONAUTH_APP_ADDITIONAL_JAVA_ARGS=-Djavax.net.ssl.keyStore=/fusionauth/example.p12 -Djavax.net.ssl.keyStorePassword=****

Our documentation may need to be updated to address this

https://fusionauth.io/docs/v1/tech/admin-guide/securing#custom-keystore

Josh

An FYI for anyone reading this in the future. The kafka integration does have been revised and include a docker based example.

@joshua Nope, was able to figure it out. I was sending the request body in JSON format instead of form URL encoded. Sorry for the late response here!

Hi @lambert-torres

Can you please provide some context as to what you are looking to achieve?

Are you storing this data on the user.data.* fields? How are you storing this data/arrays programmatically?

Thanks,
Josh

@markdoner27 This is a far-reaching question. Please feel free to post your question specifically as it relates to FusionAuth and we may be able to provide additional feedback.

-Josh

@richb201 Heya, you need to start or install FusionAuth. It's a program like MS Word or your web browser. If you haven't used it in a while, it might be stopped.

How you start it depends on how you installed it. https://fusionauth.io/docs/v1/tech/installation-guide/ has some of the methods.

@llorach-pablo It's been a while since I used .NET Core 5, but are you using a symmetric (HMAC) or asymmetric (RSA, ECC) key to sign your tokens?

The default is HMAC, but for .NET Core, I think you have to use asymmetric keys.

Here's information on creating keys: https://fusionauth.io/docs/v1/tech/core-concepts/key-master

Here's information on setting the signing key: https://fusionauth.io/docs/v1/tech/core-concepts/applications#jwt

@pclark it's macOS

@lambert-torres

Hiya,

There is no way to update a user Id after the account has been created. However, you can always specify a valid UUID when creating a user (and, indeed, most other FusionAuth resources).

Simply provide a valid UUID on the path of the POST request.

https://fusionauth.io/docs/v1/tech/apis/users#create-a-user has more.

Based on what you shared, that should work. Let me know if there's nuance I missed.

Thanks for using FusionAuth!

Dan