Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SEC-1490: Google App Engine authentication support #1729

Closed
spring-projects-issues opened this issue May 28, 2010 · 2 comments
Closed

SEC-1490: Google App Engine authentication support #1729

spring-projects-issues opened this issue May 28, 2010 · 2 comments

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented May 28, 2010

Luke Taylor (Migrated from SEC-1490) said:

Direct support for authenticating users in GAE. This would probably consist of two parts:

  1. an AuthenticationEntryPoint which calls the GAE UserService to provide an authentication URL (http://code.google.com/appengine/docs/java/users/overview.html)
  2. A standard JEE Pre-Authentication configuration, accessing the servlet API to obtain the user ID (http://code.google.com/appengine/docs/java/config/webxml.html#Security_and_Authentication). See SEC-1093.

By using the pre-authentication framework, we can easily supplement the limited functionality that GAE appears to provide in terms of user roles etc.

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Aug 5, 2010

Luke Taylor said:

For the time being, this has been implemented as a sample application (see http://blog.springsource.com/2010/08/02/spring-security-in-google-app-engine/). It's not clear atthe moment whether we need direct support within the framework.

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Feb 6, 2016

This issue depends on #1344

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants