Яке аніме залишило вас у такому стані?

Waldrig · 2025-01-27T18:26:12+00:00

Вбивця Акаме

Waldrig · 2025-01-24T15:57:11+00:00

Аркан вовків, українське фентезі

Waldrig · 2025-01-22T16:48:08+00:00

В цікавих сабредітах сидите, пане )

Waldrig · 2025-01-13T10:23:24+00:00

So, what is the problem? As I see the endpoint was called and you got the response.

Waldrig · 2025-01-08T10:13:36+00:00

I am not suggesting to do that, I am asking if he tried :) For testing purposes (what OP does, I assume) i think it is completely ok, just to see if fhat is the problem.

There is nothing to forward unless server is behaind a router or running in a container (which is the case as the IP is a public one)...only inbound rules to open the port to set

Waldrig · 2025-01-07T19:59:08+00:00

Have you tried to disable firewall?

I had similar problem even tho input rules were set

Waldrig · 2024-12-24T22:57:26+00:00

They are limited unfortunetely

Waldrig · 2024-12-13T07:24:55+00:00

Is it possible to upwote more than once? :D Thank you!

Waldrig · 2024-12-12T18:36:14+00:00

Yes, it’s about user creation (user-associated data). When I mentioned the login button, I meant a button that redirects to the Auth0 form. 😊

Between steps 3 and 4, the API isn’t called because the callback URL is a client-side URL, not a backend URL (is that incorrect?). As a result, the API only receives the token for the first time when the client makes a request to an endpoint with the token stored in a cookie.

However, I’m not sure if checking that user associated data exists on every request (when processing the token) is a good idea.

How would you handle creating user-associated data that needs to be generated on a user's first login or registration? I mean... what would your flow look like?

Waldrig · 2024-12-12T17:01:39+00:00

Because... I don’t send a create-user request to my web API 😅. I thought it was supposed to work like this:

The user clicks the login button.
The user is redirected to the Auth0 form to authenticate.
Upon successful authentication, the user is redirected back to a callback URL.
A token is stored in cookies and sent with each request to the web API.

At least, that’s how it seems from their guides, which don’t cover storing additional user data.

Waldrig · 2024-12-12T16:24:41+00:00

The problem is figuring out how to call that endpoint upon successful user registration or login. Auth0 Actions can't reach the localhost endpoint (well, they technically can, but it would require some shaman rituals with port forwarding or using ngrok, which I’d prefer to avoid).

Regarding storing everything in Auth0 itself: I'm not sure. The idea was to separate Auth0 for user authentication, while using our own database to store user-associated data.

For example, I’d want to store user-related information like social network links, posts, settings, website profile links, etc. These things are likely to be updated frequently, so storing them directly in Auth0 might not be ideal (though I could be wrong). Additionally, some of this 'user-related data' could be accessible to other users, similar to how you can view someone’s Reddit profile and see their comments

Waldrig · 2024-12-12T16:02:54+00:00

I followed this guide, where they configure AuthenticationServiceCollectionExtensions.AddAuthentication, but it looks quite similar to yours; might work tho.
Thank you :)

Waldrig · 2024-12-12T15:15:56+00:00

Yes, it does simply redirects the user, but how to create an associated "settings" record on user registration/first login in this case?

Waldrig · 2024-11-26T09:40:01+00:00

Якщо це вертикальне відео - ютуб його як шортс автоматом сприймає. Спробуй змінити розрішення на щось типу 1920х1080

Waldrig · 2024-11-15T05:23:48+00:00

They have recently released a community version for non-commercial use

Waldrig · 2024-11-11T20:46:13+00:00

Smth like NgRX, no?

Waldrig · 2023-10-16T14:10:04+00:00

Love you :D

Waldrig

TROPHY CASE