I found a stackoverflow answer from 2019.
"FusionAuth does not currently limit the number of active sessions a user may have in your application or in our SSO"
Is this still the same? Any plans for this feature?
These webhooks are often ingested into a SIEM
This is one use case. Agreed.
There might be some applications where UI has to update based on user actions related to MFA on fusionauth pages.
We are using some work arounds for now. But, I think without these webhooks, MFA is incomplete feature.
@dan Do you have any plans to give preference in community support for starter plan users?
Some kind of badge to prioritise responding to starter plan users?
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
We have a feedback from security expert.
When we signup with an email on registration page, page behaves differently when the email already exists. This gives information to attacker to filter out which emails exist.
Is it possible to configure the UI to behave similarly irrespective of whether email already exists or not. But, no verification email goes out if the email already exists.
It's been a while.
Is it something that can be planned in future?
I wrote my analysis here https://github.com/FusionAuth/fusionauth-issues/issues/1939
Can you please release a patch for updating the code.
Yes, that's correct.
In android app, we are using oidc react-native library.
The screen gets stuck after clicking login button.
Expected : Open fusionauth login page in in-app browser
There is an error message
[Error: Invalid origin uri android-app://com.example/]
I provided steps to reproduce in the github issue : https://github.com/FusionAuth/fusionauth-issues/issues/1443