fusionauth-jwt VS amplify-js

FusionAuth is one of the most decorated and successful open-source IAM solutions. It has been downloaded by more than 10 million customers and hosts over 1 million digital identities.

Ideally, I would recommend not handling and storing passwords yourself. It is preferable to use an identity provider (IdP), such as Azure AD B2C, Auth0, or FusionAuth. These systems are designed to manage your users' identity (including their passwords) so you don't have to. You could also use Single Sign-On with cloud providers.

Check out https://fusionauth.io/

Concur.

Another data point. Our open source JWT library[0] and Java client library[1] both target Java 8 because that is widely used.

0: https://github.com/FusionAuth/fusionauth-jwt

1: https://github.com/FusionAuth/fusionauth-java-client

FusionAuth | Senior Java Engineer, Senior TechOps Engineer, Senior Support Engineer | Full-time | Denver CO, USA | https://fusionauth.io

FusionAuth is the authentication and authorization platform built for devs, by devs. Our software solves the problem of integrating essential user security without adding risk or distracting from the primary application.

Ya know, the one with the features your users want to pay you for.

FusionAuth comes without the risk and complexity that typical identity systems have. With self-hosted or cloud installation, extensive documentation, free options, fast deployment and a no-hassle process, we eliminates hurdles that make it hard for developers to meet their authentication and authorization requirements.

We aren't VC funded, but we are profitable, growing fast, and need your help. We are currently hiring for the following roles:

Senior Java Engineer

Senior TechOps Engineer

Senior Support Engineer

Learn more, including salary info, what makes us tick, and role expectations, here: https://fusionauth.io/jobs

But I rarely see a comprehensive comparison that is current for any of them. And then there are others out there like Teleport and FusionAuth.

JWT processing for java. Fast: https://github.com/skjolber/java-jwt-benchmark

This article is based upon a presentation from Dan Moore of FusionAuth.

FusionAuth is a powerful identity and access management platform that makes it easy to add authentication and authorization to your applications. In this blog post, we'll explore how to integrate FusionAuth with a Python Flask application using OAuth 2.0, covering features such as login, displaying user profile information, and logout functionality.

One note of caution, though: Amplify uses a frontend-only Cognito integration that stores long-lived, never-rotating refresh tokens in browser storage, where any XSS vulnerability would have access to them. A more secure approach is to implement a couple of backend API routes to store the refresh tokens in `HttpOnly` cookies instead, which I outlined here (option 1 in your case to support SSO). I'll probably open source a solution to do this early next year so we don't all have to keep reinventing this wheel (probably why AWS calls their conference re:invent).

I'm ramosbugs on GitHub (that comment is mine). If you subscribe to https://github.com/aws-amplify/amplify-js/issues/1218 I'll post a comment there once I release a solution.

Amplify also lets you host a backend, which it runs in Lambda functions. You don't have a lot of control over it, but it works well for its intended audience: People who wouldn't know what to do if they had a lot of control over their Lambda functions. Amplify also lets you consume other AWS services easily, through declarative and easy-to-use libraries. That way, you can consume Cognito or S3 from the frontend without knowing a lot about Cognito or S3. Here's the complete list of libraries for Amplify, and you can check the Readme of the JavaScript one as an example of its features.

Whenever I call Storage.put() inside my React Native (with Expo) application, I get an error of [TypeError: undefined is not a function]. Doing some internet digging, after hours of searching, I found only one other reference to this kind of error, and that is with the DataStore: https://github.com/aws-amplify/amplify-js/issues/10764

Hello! Can you please create a GitHub issue here for us to investigate this further? https://github.com/aws-amplify/amplify-js/issues

Thanks for bringing this up. This discussion on the project's github is equally insightful on the subject.

Amplify GitHub Issue

Bug: There is currently, at the time of writing, a bug in Amplify that does not allow us to use the voiceId “Kevin”, which we selected when creating the backend resources. Selecting the voiceId “Amy” works, so we will use that.