Thanks for filing a github issue as well!

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

Hi @tl-fa,

You can view our Roadmap Guidance regarding how features are implemented into FusionAuth. A good snapshot of current development can be found here as well.

We will certainly update any related issue cards as development moves forward!

Thanks!
Josh

@maarten,

Glad that you got this working! If you have any other tips about how you got it working, that might help other users in a similar situation.

Glad it worked out!

Thanks,
Josh

A duplicate of https://fusionauth.io/community/forum/topic/438/password-complexity-rules

But the easiest way to see this is in the tenant API, since that is where they are configured.

At time of writing, here are the options.

Screen Shot 2021-05-12 at 1.50.12 PM.png

Awesome, glad to help.

Just to be transparent, application theming requires a paid edition license. You can buy one here: https://fusionauth.io/pricing/editions/

Here was some feedback from other users:

I have a k8s cron job that queries the FA eventLog API and sends them as DataDog events, then depending on severity a DataDog Event monitor will fire. Other than that, I feel rather blind.

we havent been able to upgrade quite yet, but 1.26 added a prometheus endpoint
right now we use the datadog jmx integration to get some stats, and we also do things like http monitoring

Here's the prometheus endpoint docs: https://fusionauth.io/docs/v1/tech/tutorials/prometheus/

It looks as though Trend Micro (or whatever security solution is being used as a pass through) is modifying the URL and not properly preserving the URL encoding. You will need to inquire with Trend Micro about why this would be occurring.

Interesting, not sure how this would happen. Thanks for the report @stuart-auld - I agree, this is not a good dev experience. We will identify this cause and try to failure better.

Tracking via GitHub Issue #1217

An update! The client credentials grant is now available in paid editions of FusionAuth.

Here is the documentation:

https://fusionauth.io/docs/v1/tech/oauth/#configure-entities

https://fusionauth.io/docs/v1/tech/oauth/#example-client-credentials-grant

Did you ever find a solution @developer ?

For the first issue, did you turn off client authentication in the FusionAuth application OAuth tab?

And now it works fine with 152 threads connected, so unable to reproduce this.

I'll keep an eye out for this behavior and file an issue if it pops up again.

For the record:

FusionAuth 1.27
installed via zip file
Mysql 8.0.23 installed/managed via homebrew on the mac.

We were working on getting it documented and it shipped yesterday. Sorry for the delay!

https://fusionauth.io/docs/v1/tech/apis/entity-management/ outlines all the relevant APIs, including entity CRUD.

You might also be interested in the client credentials grant, one of the main use cases:

configuring entities for the client credentials grant: https://fusionauth.io/docs/v1/tech/oauth/#configure-entities an example client credentials grant: https://fusionauth.io/docs/v1/tech/oauth/#example-client-credentials-grant

@Moonshine,

Glad you found it in our UI!

Thanks,
Josh

No, it is more like terminating an EC2 instance. All data is lost.

If you have user data you'd like to retain, please request a database dump before destroying your deployment.

Posting here in addition to GitHub: The issue for me was that the signing key didn't have the right Apple-provided key identifier, which goes in the kid field of the client_secret JWT header. Recreating the private key with that identifier fixed the issue.

A couple of options:

You could optionally configure a different template for each tenant so you could hard code the correct URL in each template.

You could also add the correct URL to the tenant.data and then pull it out in the template during render so you could use the same template across tenants.

If the state parameter is working well for you for other APIs, you could open a feature request in GH to add this to the API in question.

You're getting an error during Tomcat startup while trying to bind 9011. FusionAuth will bind 9011 by default, so if you have anything else listening on that port startup will fail.

You can shut down anything else using that port, or change the default port FusionAuth is using so that you don't conflict with other valid services on the system.

See the config reference for changing the ports. ( FUSIONAUTH_APP_HTTP_PORT )
https://fusionauth.io/docs/v1/tech/reference/configuration/

❗ Move slowly - make sure to fully decouple production and dev instances. Some pointers or guideposts--

Assuming you're running on your own infrastructure.

Clone the production FusionAuth DB Point a new dev installation to it Caveats: If you have webhooks enabled that may start making requests out to prod infrastructure from a new “dev” instance. If you do have webhooks, you could start it up air-gapped and then disable everything that could contact an external system before you enable outbound traffic. As long as the dev instances are the same version or greater it should work. You wouldn’t be able to attach the db to an instance running an older version than the schema.