Active Directory
Not planned
We are looking into integrating Active Directory (AD) into Connections Online 4.0. The first big advantage to this would be single sign-on capabilities, but, as people who administer AD know, it can be used for much more than keeping track of logins.
Since the Web server would need to be in their AD domain, AD integration will only work for people running the COL4 server in-house. This limits its usefullness to the overall product, especially when I expect to have more people using our shared server than hosting it themselves. Maybe I'm wrong, though. Is there a way we can easily allow integration with AD for people using our shared Web server?
So far, the only part we are going to have integrated for the initial release is the ability to tie your Windows login to your COL4 login for single sign-on. Are there other ways that you would like to see us integrate with AD? Would it make sense to pull in new user information or create the same organization structure in COL4?
Let us know! 
-
When we do a single sign-on (SSO) solution that allows organizations to connect using their internal Windows accounts, it will most likely use a more web-friendly technology like OAuth or OpenID to connect to a web-facing server in your organization that can then authenticate with your internal AD / LDAP / Windows Domain accounts, so it looks like we won't have to work directly with AD.
Please sign in to leave a comment.
Comments
1 comment