I need to build multiple rail applications for a customer. I would like to give them all the same user authentication system so that The user must remember different login credentials for each app. These are strictly internal applications; OpenID is not an option for this organization.
I am planning to create a central rail application to handle authentication. Other applications take the submitted user ID and password and send a request to the ate app, and perhaps a string of UAMs describes the user and their roles back.
Is this a proper approach?
(Note that due to organizational constraints I have to solve a Redhat on my own Linux 5 server using MySQL, Apache and Rail.)
Looks right for me as you describe, I can install a certification application myself, and then the form of web service Use in client applications to access certification in. You can essentially make your own in-house openID-style system.
If you have not used ActiveResource before, then Railscast and is a good place to start.
Comments
Post a Comment