We should wrap this up into a nice SDK.

Feature request opened here: https://github.com/FusionAuth/fusionauth-issues/issues/2088

@jbtruffault Thanks! The admin UI has minimal customization, but appreciate you raising the issue. It's on the list.

If logging out of a website triggers a file download in Firefox, it could indicate an issue with the website's code or with the way the logout process is implemented.

@dan

Yes, it was helpful, thank you very much!

The only thing I didn't see but I figured out is setting the Id Token signing key to OpenID Connect compliant HMAC using SHA-256.

What I did is set manually that property and took a look at the logs. There I found the new value of it and added that to kickstart.json.

I am curious if this is working because I set the algorithm and the accessTokenKeyId as follows:

"algorithm": "HS256", "accessTokenKeyId": "#{FUSIONAUTH_DEFAULT_SIGNING_KEY_ID}",

and I added let's say a random uuid for the idTokenKeyId, or it is working because I added the hard coded idTokenKeyId which gives me the OpenID Connect compliant HMAC using SHA-256 name and value.

@raghebmichael said in Manually verifying a JWT:

Something is very wrong. I don't know if this is something anybody else is facing, but I changed to a RS256 key and used the public key on jwt.io and it is still invalid. I cannot validate a JWT outside of /api/jwt/validate. This is a really big deal to me to be able to do something as simple as validating. Please let me know if I am in error, but if I can't get this to work I cannot continue using fusionauth and that's a big bummer to me as I had high hopes for this service.

b63ceaca-e17c-48e4-b7cc-fe757eff696f-image.png

This is exactly what I was looking for to solve my problem.
Thank you very much.

@olly

Hmmm. It seems as though you have self service registration enabled. If this is the case, when an existing user registers for an application, the FusionAuth registration is automatically enabled.

Maybe I don't understand what you are trying to accomplish. Could you explain what you are trying to do?

Thanks @harish_reddy !

Per this comment, this is slated to be fixed under https://github.com/FusionAuth/fusionauth-issues/issues/1894 .

This is planned for 1.43.0, which is the next release.

Thanks.

@g-natsoulis

Hiya, can you explain a little more about what you are looking for? I'm not quite sure what you mean by "an OTP provider for an Exchange server that has ADFS authentication set up?"

@fusionauth-0

Hmmm. So you are saying that:

you can connect from the ec2 instance to your postgresql instance. you can connect via the web to the fusionauth instance, but it is stuck in maintenance mode.

Where is the postgresql instance running? Is it on the same ec2 instance as FusionAuth?

What value are you putting for the hostname?

@eduards-celmins It is not built into FusionAuth, but if you use an email provider, they'll often provide such functionality.

Here's information about sendgrid: https://docs.sendgrid.com/ui/analytics-and-reporting/stats-overview

I believe there are similar stats captured for other email providers.

@langnerfrancesco What version of FusionAuth are you using?

What version of postgresql?

@vvicazz That's great news!

IMG_5038.jpg

@bharath-yadavally You could absolutely use the 2 step approach you outlined. There are two different approaches that have different strengths and weaknesses.

The tradeoffs are that if you make those two calls, you're depending on the identity provider to be up and available to your backend service. You're tightly coupling the backend service to the identity provider.

That can work fine, but as you scale, more and more backend services will be making those calls, and the idp and speedy connections to it become more and more critical to your application.

Contrast that with the webhook approach, where the data is pushed to every backend service, and only when a user is deactivated. In this case, there'll be far less coupling with the identity provider, at the cost of more complexity on the backend service side.

Hope that helps.

@kushalborda1997 Hiya,

We recently updated the documentation to make it more clear you shouldn't use the /api/jwt/reconcile endpoint for any identity providers except the external JWT provider. We'll change the application to make the error message clearer; here's the tracking issue: https://github.com/FusionAuth/fusionauth-issues/issues/2074

You should use the OIDC provider and the complete login endpoint. Here's documentation that should help: https://fusionauth.io/docs/v1/tech/apis/identity-providers/openid-connect#complete-an-openid-connect-login

Hope that helps!

@didier I'm not sure I understand.

You are saying you want to send the registration email yourself, not automatically with FusionAuth?

(There are two possible verification emails. One is for a user creation, which verifies their email whenever someone creates a user, for any application. Another is for registration verification, which again checks their email but only when someone registers for a certain application.)

If that is the case, use the skipVerification and skipRegistrationVerification settings if using the API. There are analogous settings in the admin UI as well.

More documentation here: https://fusionauth.io/docs/v1/tech/apis/registrations#create-a-user-and-registration-combined

and here: https://fusionauth.io/docs/v1/tech/core-concepts/applications#registration

and here: https://fusionauth.io/docs/v1/tech/core-concepts/tenants#email

@jose-cardenas Hmmm.

Can you tell use anything more?

Are you able to create users with the API?

Have you set up the ingress proxy correctly, making sure you are sending the correct headers. More doc here: https://fusionauth.io/docs/v1/tech/admin-guide/proxy-setup

Did you follow the kubernetes installation guide?

@dan

User logs in through authorization code grant flow

Here goes the refresh token settings for the application:

e34e22da-b37b-41e6-8816-88b43a8cbddd-image.png

FusionAuth version being used is 1.36.6

Thanks,
Vindhya

@jesper Sorry to hear about the issues.

Can you try setting the http version, as outlined here:

https://fusionauth.io/community/forum/topic/2254/having-an-issue-with-nginx-in-front-of-fusionauth