action #1276
closedDB based user access control (with tests)
Description
Add users support to the application. No integration with iChain at this point, just users in the openQA database.
Updated by ancorgs almost 11 years ago
- Priority changed from Urgent to Immediate
Updated by alarrosa almost 11 years ago
- Assignee changed from ancorgs to aplanas
Updated by ancorgs almost 11 years ago
Looks like this is the most common option for implementing authentication in Mojo. Looks to be in pretty good shape.
http://search.cpan.org/dist/Mojolicious-Plugin-Authentication/
This one is more high-level and looks nice... but it's advised as "pre-alpha prototype" with no updates in one year :-(
https://github.com/koorchik/Mojolicious-Plugin-UserManager
Some more info about implementing authentication:
http://mojocasts.com/e3
Updated by ancorgs almost 11 years ago
This plugin looks like a perfect choice for our problem https://github.com/hayajo/Mojolicious-Plugin-Web-Auth Looks active and reasonably documented, and there is an example application in github https://github.com/dokechin/webauth
In case we decide to write something from scratch or go for something simpler, here we are some properly documented code that can be used (as it or as inspiration):
https://github.com/pgraemer/Mojolicious-Plugin-HttpBasicAuth
https://github.com/sshaw/Mojolicious-Plugin-DigestAuth
https://github.com/marcusramberg/Mojolicious-Plugin-OAuth2
Updated by aplanas almost 11 years ago
- Status changed from In Progress to Resolved
To test the openID integration:
1.- Go to /login
2.- Use the suse openID server: https://www.suse.com/openid/user/
3.- Go to the test page /secret/test
The white list is in the Login.auth method.
Updated by ancorgs almost 11 years ago
Testing the new openID login. Committing small fixes and a temporary way of displaying the logged user.