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.

Archive /

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

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

Single Sign-On and Batch Loading

Go to End



Community Member, 7 Posts

3 June 2008 at 10:19am

I'm new to SilverStripe, but have been evaluating/playing with it for awhile. I'm attempting to acquire/create a more functional intranet service within my corporate environment. SilverStripe appears to be good for most of the required functionality. This environment is largely Microsoft of various flavors and uses Active Directory for authentication.

I have a couple of fundamental suggestions for improving SilverStripe's ability to compete in this marketplace.

1) Single Sign-On

Lancer's External Authentication module is a step in the right direction, but doesn't go quite far enough. My users expect their morning login to the corporate environment to be enough. If they are presented with a login screen from an internal app - they call IS - 'It's obviously broken'. In order to be viable in this environment, SilverStripe must play along. If a browser carries authentication tokens, it must automagically allow the user access.rights appropriate to their AD group. The 'create a member on the fly' mechanism in the current implementation doesn't seem to pass AD group information into SilverStripe. It uses a default value. This means manually adjusting 800 or so group assignments once they've all logged into the site.

2) Batch Loading

.1) Given the environment above, obviously an ldap based batch load and an ongoing synchronizaton job could be part of a viable solution for the Single Sign-On.
.2) Need to be able to batch load preexisting content. How long will it take me to load 800 employee photo's - selecting them one at a time? Can't I move them into a directory then run a program to load them into the CMS db? Then I can start in on the 500+ documents. A batch load could help there, but won't solve all of the reformatting problems - alas :).

Thanks for listening. Love to hear ideas for solutions...