@jawaid-karim Are you setting all the headers mentioned here? https://fusionauth.io/docs/operate/deploy/proxy-setup

If you needed to, you could always build an API integration (the User Update API lets you reset passwords, or you could initiate a Change Password Request) into your application for a specific user.

@thomas-wojeck

Have you turned on the debug logs and looked in the event log? That's what I'd start doing to troubleshoot.

More here: https://fusionauth.io/docs/operate/troubleshooting/troubleshooting#enabling-debugging

@info-0 are you able to use our global one?

https://local.fusionauth.io/ will redirect to http://localhost:9011

If not a great option is to setup ngrok
https://fusionauth.io/docs/get-started/download-and-install/development/exposing-instance

ngrok http --request-header-add 'X-Forwarded-Port:443' 9011

@fusionauth-qhj5e I have brought this up internally, for now we are considering adding a PR to make it more clear for users.

https://github.com/FusionAuth/fusionauth-site/pull/2918

@ryan-hopper Thanks for sharing that info. Appreciate it!

@pradhanv88 it is documented here: https://fusionauth.io/docs/reference/configuration

But there is a bug with TLS in recent versions of FusionAuth: https://github.com/FusionAuth/fusionauth-issues/issues/2498

This is scheduled not for this release, but for the next one.

I was able to get this working with:

jdbc:postgresql://db:5432/mydb?currentSchema=auth

@renukamirihana Have you been through this page? https://fusionauth.io/docs/operate/deploy/proxy-setup

What message to you receive when the application goes to the unauthenticated path?

Are you attempting to enable users to log into your application using Google? Click Here for further details

@asenjowork Awesome, I'm glad you figured it out!

Hiya @youchuan990316 You should be able to do this using javascript. I'm not familiar with particular libraries or methods, but google has a number of options.

You can modify the Account two-factor enable theme page.

Hope this helps.

@harish_reddy Thanks for the feedback, we appreciate it. While I think it is unlikely we'd separate out those webhooks, you are welcome to add a GH issue with your feedback and we can see how others in the community feel about the topic.

@tiago Awesome!

Hiya @harish_reddy ,

That's a cool idea. We don't have any plans to do so right now.

@ronn316 Awesome, glad you got it the way you want it and thanks for sharing the update with the community!

@ccurtis Are you able to create the Administrator account?

@netstack said in Setting fusionauth-app.http.cookie-same-site-policy to none in Version 1.4x:

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

It does look like the fusionauth-app.http.cookie-same-site-policy has been deprecated as of ver 1.37.0 and I do not know of another way to set it. As browsers are moving away from 3rd party cookies, I think this makes sense.

There are a few options.

the admin UI application is in the default tenant and can't be moved, so add all other users to a new tenant. This adds an additional layer of separation use the IP ACLs function if you are on the enterprise plan use a proxy and have the proxy filter out traffic that doesn't originate from the office network and is requesting anything with the FusionAuth admin UI client id (which is immutable)