Thank you for this i have managed to get past the issue with the database i changed to to postgres SQL and it worked fine, I'm just to figure out if i can ass Exchange 2016 to this application so users are made to get a Auth code before they can logon to exchange.
We don't have any documentation like this. And I'm not aware of anyone doing this--but of course with thousands of installs we're not aware of how everyone uses FusionAuth 🙂 . I'll ask around and point folks to this, maybe someone in the community has on the ground experience.
However, when I look at the okta docs, they are using OIDC, so FusionAuth should be usable with a very similar nginx config. If you look at the OAuth endpoints docs you should be able to figure out the pieces that nginx needs (jwks endpoint, etc).
There's no formal recommendation for how to integrate with FusionAuth, other than the APIs.
The way I'd build pages and logic that I wanted side by side (like a login page which required two factor auth for a given application 🙂 ) with FusionAuth would be to proxy fusionauth with something like an ALB or nginx. Then have one path for fusionauth login pages and another path for your custom application. You could pull the retrieve the theme CSS and reuse it.
By tracking the correlation ID, I found that the reply url mentioned in the request is ending with OneDrive/ but the reply url configured on the application (with client ID in above error) is ending with OneDrive (without a slash at the end).
Kindly update reply url in the application by navigating to Azure Portal > Azure Active Directory > App Registrations > All apps > Search with client ID (aka app ID) > Under Authentication blade of the application > update the reply url with a slash at the end.
Can you confirm that you've double checked your URLs?
What will be the simplest path to integrating FusionAuth with my app?
You can self host FusionAuth, in which case, yes, docker on AWS is a valid option. There isn't an AMI or FusionAuth offering in the AWS marketplace at this time. You can self host it using any of the options outlined in the installation docs. It's hard to know what to recommend as I don't know what system technologies you are deploying other parts of your application with.
You can also use FusionAuth Cloud for a managed offering, which means you won't have to manage FusionAuth at all. Learn more about that option here: https://fusionauth.io/pricing
Can someone "map out" what I need to do at a minimum to get such system up?
I'm not sure what you're asking here. If you want help setting up passwordless, I'd review the passwordless guide. If this doesn't help, can you explain a bit more what you're looking to do?