Authress HQ

@theburningmonk To me it seemed that the pricing aligns with that of other players( e.g. @osoHQ or @AuthressHQ ). But they are all very expensive IMO. We use @AuthressHQ and have 2 layers of caching in front (in memory in Lambda & fronting their API with CloudFront).

If you're trying to figure out what auth solution is right for your project, Dorota Parad of @AuthressHQ has you covered. Check out her overview of the auth space, along with specific recs for side-projects, MVPs, B2Cs, B2Bs, and public APIs. 👇 indiehackers.com/post/adding-au…

Don't leave your app security up to chance. @AuthressHQ ensures generation of unique signature keys for every client and service.

Here's a reminder: Legacy systems ARE security vulnerabilities. Especially ones using PHP, XML, RPC. Remember to migrate ALL systems to using @AuthressHQ and not just your cutting edge ones. A recent find by @OTPHolidays reminds us of this: openbugbounty.org/reports/180701…

Accurate time servers are critical for validating security token lifetimes. This is a security relevant threat.

@AuthressHQ is proud to NOT be on this list: sso.tax

What's the #1 best way to secure a software application? All answers welcome.

We don't allow malicious actors to discover our customers IAM principals and roles because retrieving that information requires at least knowledge level access permissions.

There are so many misconceptions with JWT auth, that we just had to publish about it! medium.com/authress/jwt-a…

auth0.com/blog/why-your-… It could be, if it was true, but it isn't. @AuthressHQ charges only by what you use. And you don't need to worry about what an "Active User" is. Value isn't a step function, so pricing shouldn't be either.

Make @gitlab + @awscloud safer by eliminating access tokens and secrets. Now you can upgrade to roles. medium.com/authress/aws-g…

Today we open sourced our OpenAPI validator: github.com/Rhosys/openapi…