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

Document how to secure the whole application #10

Open
pedersen opened this issue Sep 24, 2012 · 3 comments
Open

Document how to secure the whole application #10

pedersen opened this issue Sep 24, 2012 · 3 comments

Comments

@pedersen
Copy link
Member

This issue existed in Trac. The original can be viewed at http://trac.turbogears.org/ticket/2218

This issue existed on SourceForge. The original can be viewed at https://sourceforge.net/p/turbogears2/tickets/14

@pedersen
Copy link
Member Author

Original Author: pedersen, Original Timestamp: 2011-03-10 03:46:16.297000

Original Body: We should explain how to secure the whole application, while excluding the authentication-related URLs if using a repoze.who !RedirectingFormPlugin-like challenger.

See also:
http://groups.google.com/group/turbogears-trunk/t/97c0e11a4d538a1d

@pedersen
Copy link
Member Author

Original Author: amolsf, Original Timestamp: 2012-04-03 19:27:21.627000

Original Body: This is probably achievable in a more TG way of doing things by using _lookup inside of the RootController returning the object with the secured set of methods for the RootController.

This is easier and avoids having to mess with the underground authentication layer. Should probably be documented anyway.

@pedersen
Copy link
Member Author

Original Author: pedersen, Original Timestamp: 2012-08-24 01:34:54.558000

Original Body: - version: 2.1.0 --> 2.1.5

  • milestone: 2.2.0 --> 2.3.0

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

No branches or pull requests

1 participant