= Aurora Simple Authentication Server
A small scale authentication server to provide multiple applications one point
of contact for authentication against LDAP et al data stores. The system will
respond with a temporary Authenticated Token to be used for the session. There
will also be a client-side library for use in Ruby available.
The authentication server will also have a component for user management
including permissions and access management.
== Installation
$ sudo gem install aurora
== Basics
An Aurora server is created on a specific port which listens diligently for all
requests and are routed accordingly. The most basic part of an Aurora server is
the @authenticate@ block. This passes the username and password to pass auth-
entication with and will return either a new Token for future authentication
requests or false. (NOTE: These details could change.)
Essentially what you have to do is set up hooks for the server to call when a
particular action is requested, starting with @authenticate@ and then moving
on to more custom functionality.
Because the server is not designed with any actual authentication checks, it
is totally up to the implementer to authenticate users, be it through an LDAP
data store or a MySQL database. This provides a great deal of flexibility, but
a good deal of burden and responsibility. Aurora just makes it possible to
centralize your authentication outside of your applications (though, with a
little creativity, you could certainly decentralize it with Aurora as well).
== Copyright and Licensing
Copyright (c) 2007 Matt Todd <http://purl.org/net/maraby>.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
This notice is located at: http://www.opensource.org/licenses/mit-license.php
A small scale authentication server to provide multiple applications one point
of contact for authentication against LDAP et al data stores. The system will
respond with a temporary Authenticated Token to be used for the session. There
will also be a client-side library for use in Ruby available.
The authentication server will also have a component for user management
including permissions and access management.
== Installation
$ sudo gem install aurora
== Basics
An Aurora server is created on a specific port which listens diligently for all
requests and are routed accordingly. The most basic part of an Aurora server is
the @authenticate@ block. This passes the username and password to pass auth-
entication with and will return either a new Token for future authentication
requests or false. (NOTE: These details could change.)
Essentially what you have to do is set up hooks for the server to call when a
particular action is requested, starting with @authenticate@ and then moving
on to more custom functionality.
Because the server is not designed with any actual authentication checks, it
is totally up to the implementer to authenticate users, be it through an LDAP
data store or a MySQL database. This provides a great deal of flexibility, but
a good deal of burden and responsibility. Aurora just makes it possible to
centralize your authentication outside of your applications (though, with a
little creativity, you could certainly decentralize it with Aurora as well).
== Copyright and Licensing
Copyright (c) 2007 Matt Todd <http://purl.org/net/maraby>.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
This notice is located at: http://www.opensource.org/licenses/mit-license.php