Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We're retiring the forums!

The SilverStripe forums have passed their heyday. They'll stick around, but will be read only. We'd encourage you to get involved in the community via the following channels instead:

Archive /

Our old forums are still available as a read-only archive.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo

Authorization, Authentication and a pile-o-users

Go to End

2 Posts   1668 Views


Community Member, 7 Posts

21 March 2008 at 11:25am

I'm evaluating SilverStripe for possible usage for my corp. intranet site. Since we're a (mostly) microsoft shop we have an AD environment. My evaluation install consists of the core and the External (ldap/AD) Authentication module. I haven't been successful logging in with ldap - currently I get to a url that ends in Security/?executeForm=LoginForm and a blank page (reloading the blank page yields an http 500 ).

However, even when that module works as advertised - it still won't fit in our 'single-signon' environment. I have over 700 users and really can't see creating (or modifying [auth source & user ID]) them all individually.

Assuming that the problem in paragraph 1 can be resolved (advice is welcome); what is the best approach for populating the member table?

Should I write an external process to sync the table with AD in the night, then hack the login to not ask if we're already logged into the domain?

Or require the users to do a one-time login after hacking the auto-add-user code to also populate the additional fields reqd for an ldap login in a single authenticator environment?

Or is there a better approach?


Forum Moderator, 801 Posts

29 March 2008 at 4:23pm

hey dennis, i've pointed the maintainer (roel) for the ldap module to this post.