Hi Rob,
Rob wrote:
> I am looking for a single sign-on system, primarily to be used with
> OpenID, possibly Shibboleth or ldap. I like OpenID because of the
> consistency and branding a URI like myname.example.com provides.
> However this will be a "private" system, in which only IDs from
> example.com will be allowed.
OpenID per se wasn't designed to have identifiers act as a level of
access control in the authorization sense but I can have a further chat
with you on requirements to see what we can do to make this happen if
you're interested.
I also need the data to be stored in
> MySQL. Can ESOE do this?
Yes one of the supported databases is MySQL.
> I am only finding minimal info on reasonable requirements. How much
> available ram needed? Any other dependencies than tomcat5? Is it
> presumed that ESOE will be installed on a dedicated server?
ESOE as an open source project requires ongoing funding to help
development and future features etc. One of the ways we do this is by
offering professional services around ESOE deployments (and SSO concepts
in general). It's not that we are holding these numbers back on purpose
its just that we either haven't had the time or in some customer cases
been allowed to release this kind of information. Additionally we view
ESOE as a toolkit, deploying the entire thing for most uses is overkill,
generally deployments start out with a subset and add features/plugins
over time. Changing the deployment models obviously complicates this.
Generally speaking though we deploy on dedicated hardware, for larger
customers or those concerned with redundancy we deploy across multiple
nodes with Layer 7 load balancing. RAM depends on numbers you expect to
see in terms of concurrent sessions, request rates etc. Something we can
help work out when we understand your environment.
If you would like to contact me off list at bedd...@intient.com about
your requirements I would be happy to discuss this further with you.
regards,
Bradley
--
Bradley Beddoes
Lead Software Architect
Intient Pty Ltd
