Shared Code for Login Users and Management: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
=Thoughts list= | =Thoughts list= | ||
Line 31: | Line 30: | ||
===One-stop shopping=== | ===One-stop shopping=== | ||
=Packages | =Packages considered= | ||
= | {| | ||
! Login/Authentication | |||
! Roles/ | |||
! Notes | |||
|- | |||
| OpenID | |||
| OAuth | |||
| Unsure how to tie together and handle management | |||
|- | |||
! colspan="2" style="background: #ffdead;" | Drupal | |||
| Seems heavy when all we would want is the user code | |||
|} | |||
[[Category:SWUG Projects]] | [[Category:SWUG Projects]] | ||
[[Category:Software]] | [[Category:Software]] |
Revision as of 19:20, 12 July 2011
Thoughts list
Risks
Accidental erasure
(e.g. web crawlers finding the "erase all" link)
Hacking
platform targeting hackers
man in the middle after login not a worry
Wants
role-based users
Reusable user identities
If somebody did implement their own backend server, they'd be able to use it Rely on either a third-party or local identity authority For example, people could either use a server provided by or, in the case of a local app,
Simple management
Simple implementation (many languages)
One-stop shopping
Packages considered
Login/Authentication | Roles/ | Notes |
---|---|---|
OpenID | OAuth | Unsure how to tie together and handle management |
Drupal | Seems heavy when all we would want is the user code |