Any advice on Implementing an Oauth Provider with AWS Lambda?

Asked Jun 03 '17 at 18:26

Active Jun 04 '17 at 15:23

Viewed 334 times

I currently have a functional Oauth Authentication Provider implemented with Spring Security Oauth running on an AWS ECS cluster, but I would like to come up with a server-less implementation using AWS Lambda with AWS SAM. I am aware that there are wonderful SaaS providers such as Auth0, but the price for the thousands of user accounts we will require is prohibitively expensive.

I have discovered danilop/LambdaAuth, which is useful, but not OAuth. For now, I only require a client_credentials grant, which seems very simple. But I would like to be able to leverage some library which will make it easier to implement more grants and flows for the future. I have investigated python's oauth2 and oauthlib libraries, but the documentation appears to be useless for my requirements.

Does anyone have any advice on how to proceed?

edited Jun 04 '17 at 15:23

asked Jun 03 '17 at 18:26

zalpha314

1,444
4
19
34

What is the purpose of writing your oauth provider? is it for authentication or authorized access(authorization) to resources? – Ashan Jun 04 '17 at 03:08
Authentication. I've updated the question to be more specific. – zalpha314 Jun 04 '17 at 15:23

Any advice on Implementing an Oauth Provider with AWS Lambda?

0 Answers0