@muravyov-alexey

Not sure what it is need for, but if it is correct then better put some hint about this in GUI near the option.

Good suggestion! I have logged an issue for consideration.

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

Hmm. In my view, this makes sense. Here are two cases to consider

jwt.refresh-token.revoke - maybe there are some application-level events that need to take place based on this event. In the right context, this might be functionally equivalent to "logging someone out." If someone was logged out (forcibly) from your application, then you might want to take action based on that (remove them from a list, or make another programmatic check, etc).

user.action - maybe this user was actioned for any number of application-specific reasons that you might want to respond to.

Everything else is scoped to a tenant, from my understanding.

I hope this helps. Thanks for the feedback.

Thanks,
Josh

I tried with all HTTP methods enabled for /api/user only, and it update user successfully.
But if I tried only with GET and PATCH methods enabled for /api/user , I get 'statusCode=401'.
Here is code

import { FusionAuthClient, UserRequest } from '@fusionauth/typescript-client' ... export class FusionAuthService { private fusionAuthClient: FusionAuthClient; constructor(private context: Context) { this.fusionAuthClient = new FusionAuthClient(context.config.fusionAuth.apiKey, context.config.fusionAuth.apiUrl); } ... public async updateUser(userId: string, userRequest: UserRequest ) { return this.fusionAuthClient.updateUser(userId, userRequest) .then(clientResponse => { logger.info("User:", JSON.stringify(clientResponse.response.user, null, 2)); }).catch(logger.error); }

here is invocation of updateUser method that happens on 'user.registration.create' event

if (user) { const patchBody = { user: { email: event.user.email, data: { userId: user.id } }, } await this.fusionAuthService.updateUser(event.user.id, patchBody); }

Now I understand that I use updateUser method and I don't know what kind of HTTP request it used.
I have found patchUser and with it get success.

Thanks for your help.

I'd add on to what Josh is saying: it is extremely unlikely we'd switch the standard FusionAuth Cloud hosting service to CockroachDB. PostgreSQL meets our needs very well at this time.

However, it seems like CockroachDB compatibility is very close. I think there was just an issue with social logins and I believe that the FusionAuth user interviewed in the linked blog post filed an issue with them, as you mention.

Given that information:

feel free to host FusionAuth with CockroachDB in your own environment if you are interested in FusionAuth building out a special deployment for you with CockroachDB, you can contact our sales team. This type of custom work typically requires an enterprise contract.

@tomas-huber

Can you elaborate on what needs to be corrected or what errors you were seeing in our documentation? If you could link the page of documentation from www.fusionauth.io you were following and what errors you encountered, that would be great.

If it's simpler, you can also include that information on an issue card for our documentation site
https://github.com/FusionAuth/fusionauth-site

Thanks!

Thanks,
Josh

The doc has been updated and the website will be updated when it has been reviewed: https://github.com/FusionAuth/fusionauth-site/pull/1016

Ok, I found the problem.

I was sending an Authorization header, because that was the default option in Postman. Now I tried it with the other option which is "Send client credentials in body" and it works.

The documentation about the token endpoint had me a bit confused, that's why I kept sending an (invalid) Authorization header. Now that I post an empty client_secret parameter in the body and NO Authorization header to the token endpoint, things are working fine.

Thanks for pointing me in the right direction, @robotdan and @dan.

Hey Dan. It has been a long time! I just can't get past the passwordless problem I have with fusionAuth. Your help has been stellar but I really need to hire someone to get me over the "hump". Seems like there are not too many people out there that have a working knowledge of FA. I have tried to find one! Can't hire help and can't get community help leaves me with no options.

I took a look at https://fusionauth.io/learn/expert-advice/authentication/webapp/oauth-authorization-code-grant-sessions/ and will try to switch over to using this method since it seems well documented. I will probably need to find someone to update the themes if I get it going. Good luck on that!

I really like the diagram which shows the message flows in it. Is there a document, just like oauth-authorization-code-grant-sessions but for passwordless? That diagram, but for passwordless, would definately help.

Hiya @reece-temple @moricio ,

Sorry to hear you've been having trouble with this. I've installed FusionAuth many times and not seen this error, but understand how frustrating that must be.

Can you please provide the following information to help us find the issue:

What you are trying to do, specific step by step of clicks you make/scripts you've run, APIs you’ve called, configuration you have, things you’ve changed, etc. More information is better. For example, what you are seeing, specific panels in the UI, API status codes, errors, screenshots, etc. We want all of it. What you expected to see. Sometimes this is obvious, and sometimes it isn’t. Err on the side of over sharing. What you've tried already. Sometimes this can help us narrow down the issue more quickly. The version of FusionAuth you are using (this information is available on the admin screen in the lower left hand corner). The number of FusionAuth nodes you are running in your deployment. Information about supporting infrastructure such as the database and elasticsearch, including the version and architecture (is the database local, cloud managed, etc). All FusionAuth log files you can provide. Please don't provide snippets because often the issue won't be in the snippet but somewhere else in the logs. Providing us with complete log files upfront helps us track down issues faster. And you'll avoid getting replies like "please send the complete log files". Of course, please remove any sensitive information from the log files.

Additionally, if you are using mysql, you need to allow network access to download the mysql driver (due to licensing issues). This is laid out here: https://fusionauth.io/docs/v1/tech/installation-guide/system-requirements/#network-access

Thanks,
Dan

@dev

Thanks for the question!

Have you reviewed the troubleshooting steps for email?

https://site-local.fusionauth.io/docs/v1/tech/troubleshooting/#troubleshooting-email

Setting the mail.debug=true and examining the event/app logs will be most helpful in narrowing down the source of the issue.

Thanks,
Josh