@florian,

You are going to want to make sure that you are on the latest version of FusionAuth (1.29.1), as some versions may not display this option (this was a recent bug fix)

Located under Applications > OAuth > Toggle

A screenshot is attached.

Hope that helps!

Thanks,
Josh

@marcus-krassmann Thanks for the info -> we have updated the MVN repo with a more current point release.

Thanks,
Josh

@mehamm,

It sounds like you are on the right track. A few comments:

• The Web API should not persist the access token, but the web app definitely can (often in a session). The web app can then present the access token until it expires, in which case the web app can renew the access token with the refresh token.

• "Web API verifies token against FusionAuth (my app) endpoint" -> You can also verify the claims were signed by FusionAuth without calling the introspect endpoint by using a JWT library.

• "Web API pulls user claims from token for role(s) and tenant, if verified returns data back to web app." -> Makes sense. Make sure to check the "aud" and "iss" claims to ensure they are what you expect. You should do this even if you are using the introspect endpoint.
• The correct tenant can be found from the client_id, since all applications are associated with one and only one tenant.
  If you have any specific issues, please feel free to post them in the forum (a new topic might be best).

By the way, if you are running in FusionAuth in production at scale, we encourage you to get a support contract . Having one allows access to the engineering team via opening support tickets. https://fusionauth.io/pricing/. Obviously, this is not a requirement, but should your business needs require a higher support level, it is available

I hope this helps!

Hi @nileshnandaniya135!

You may want to review your SMTP settings, as this could indicate something was not set up correctly (prior to the test). Do you have any additional errors or logs that we can review with you?

Additionally, I would encourage you to review our documentation regarding setting up an SMTP service.

• Configure
• Email Overview - with debug steps
• Enabling Verbose Logging
• Email Templates

I hope this helps!

Thanks,
Josh

Hi @michael-schramm,

If you could provide a bit more context to your issue, we could perhaps give a few pointers, but unfortunately, I believe this is outside of our accepted/documented use guidelines. FusionAuth is supported using MySQL and Postgres (documentation here).

Thanks,
Josh

@minhngocnguyenduy

This is an option on the user object (in the admin ui users > edit user > image url)

Hope this helps!
Josh

@oleksiikraieviy and @vindhyahegde2114

This is going to be related to how you set up a generic messenger - I have a few tips here.

https://www.loom.com/share/cdd0835c054b40a4a3a6e2e32f1c9d04

Thanks,
Josh

1.30 is released

Release notes forming
https://fusionauth.io/docs/v1/tech/release-notes/

Hey FusionAuth Community!

Just a heads up -- we have made a few revisions to this post!

If you are interested in using VueJS and FusionAuth -- check it out!

https://fusionauth.io/blog/2020/08/06/securely-implement-oauth-vuejs

Hi bogorad,

The functionality that you are looking for is located in the themes section of the FusionAuth application. Specifically, you will want to review all OAuth pages (OAuth authorize and possibly others) to adjust the template to your user requirements. FusionAuth uses FreeMarker for templating.

Additionally, below is a link to our documentation regarding themes (as well as a very useful video on how to mimic a custom Stack Overflow login page, for instance)
https://fusionauth.io/docs/v1/tech/themes/

Hopefully, that sets you on the right path! Enjoy FusionAuth!

Thanks,
Josh

@williamjeanmireault

It sounds like you would like to be able to read state or similar in a lambda (we don't currently allow this)

In a populate lambda, you do have access to

• Entity Data (https://fusionauth.io/docs/apis/entities/entities) (entity.data)
  This means that you can set any custom field you would like on your entity and use that in a populate worklfow
• .fetch() https://fusionauth.io/docs/extend/code/lambdas/#using-lambda-http-connect

So you could access custom data attributes or call out to another system in the lambda

If you have access to a support contract, you can also log a support ticket if you would like or open a feature request outlining your requirements
https://fusionauth.io/docs/operate/troubleshooting/technical-support

@dan Also, depending on the workflow, if a user does NOT federate but does NOT check "trust this computer" they will NOT establish "MFA trust". Without trust, a user will be prompted to MFA again. Of couruse, With "MFA trust", they will not be prompted. This answer is implicit to this conversation, but MFA policies and FusionAuth center around this check box and trust (with the current edge case of Federation noted).

I'm seeing this message:

exec /usr/local/fusionauth/fusionauth-app/bin/start.sh: exec format error

when I try to upgrade FusionAuth. I'm running containers.

@dan continuing in a support thread.

Note for future folks -

Resolved under this issue https://github.com/FusionAuth/fusionauth-issues/issues/1742

And in version 1.44

https://fusionauth.io/docs/v1/tech/release-notes#version-1-44-0

@imsurya2442

Thanks for the question.

This may be related https://github.com/FusionAuth/fusionauth-issues/issues/2019. If it is, there is a workaround listed that you could attempt.

Thanks,
Josh

@lambert-torres replied out of band to this forum. This may have been addressed in version 1.38.0 and beyond.

Thanks,
Josh

@david-cheal

Since FusionAuth hosts each customer on their own servers (you are not sharing hosts with other customers as in a traditional SaaS model), you can determine when (or if) you want to upgrade your server in FusionAuth Cloud.

• https://fusionauth.io/docs/v1/tech/installation-guide/cloud#upgrade-duration

If you would like to further weigh your options, you can reach out to our sales team for advice on what may best support you.

https://fusionauth.io/contact

Thanks,
Josh

@stefan-0

Thanks for the question -- I don't think that this will work in the way that you intend.

I would have to test to be sure, but if FusionAuth cannot make the user (based on your chosen user provisioning policy), then this user will not be created and thus not linked, and therefore this event will not fire.

https://fusionauth.io/docs/v1/tech/events-webhooks/events/user-identity-provider-link

Depending on your desired outcome, it might be best to change your linking strategy (to create this user when linking) and then use user.create webhooks. You could fail this transaction if certain requirements are not met (thus the user will not be created and linked).

I hope this helps!

Thanks,
Josh

@quent Thanks for the question!

To note, each IdP will handle logout differently. It would be hard for FusionAuth to know how to log each user out of disparate systems. Killing each user session is specific to that IdP implementation. In the FusionAuth logout process, we will call a logout endpoint of your choosing. In that endpoint, you could have your integration call the IdP to remove the user's session.

I hope this helps!

Josh