@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)

@mike123 Can you please try with a capital "S" vs lowercase "s?"

php -S localhost:9012 -t public

@matth Hmmm. Well it should work. If it doesn't, that's a bug.

But in this case, we need to decide to change the linking strategy. If it set to email, this approach will generate new users, rather than linking social login.

Sure, that would be a problem. You'd need to store the GH login id and make sure the user associated it somehow. It's a thorny problem because at the end of the day, the user has decided not to make their email available.

I thought it could be possible because reconcile Lamba would receive a user access token as a parameter. At least such an idea appeared when I saw the lambda signature.

I don't see where the user access token is presented to the GH api. Maybe I'm missing something.

@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!