Topics created by harish_reddy

We also noticed that even with silent renewal, MFA code is getting triggered. This is very annoying for our users who stay on the page for long time.

Is there a way prevent MFA for SPA on every token refresh?

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

@harish_reddy I just want to make sure I understand where you are coming from. If you user signs up with an email address, you want the same response even if they are already signed up? Can you please share some images of how you would like the flow to work? I think this could cause problems and confusion the way I am thinking about it.

@harish_reddy

You are asking if there is a way for the client to somehow know the user's account on the server has been modified and therefore refresh the JWT? I suppose you could have the server somehow push info to the client using something like websockets.

Or are you asking if the client can check every so often and refresh the JWT even before it is expired? In this case, you could shorten the lifetime of the JWT, or just refresh the JWT periodically using this API: https://fusionauth.io/docs/v1/tech/apis/jwt/#refresh-a-jwt

Or am I misunderstanding the question?

@alickabrook1
I was not setting origin URL in mobile app.

I was setting it in fusionauth config.

Shared screenshot in https://github.com/FusionAuth/fusionauth-issues/issues/1443

@harish_reddy thanks for letting us know!

I created a PR to fix this and will get it shipped in the next few days.

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

Cheers!

Ah, I see. Yes, this is new functionality; the javascript redirect is the best option currently, but that won't automatically log a user in.

If you have a support contract, please open a support ticket.

Otherwise, please file a feature request in our github issues repo.

Hello,

It's been a while.

Is it something that can be planned in future?

As of version 1.29.0, we've added a lot more SAML debugging. I'd be interested to know if anyone else runs into this issue and if the extra debugging helps resolve the issue more quickly.

Cheers!
Dan

Looks like this might be an issue you'd want to upvote: https://github.com/FusionAuth/fusionauth-issues/issues/439