Skip to content
This repository has been archived by the owner on Jul 24, 2020. It is now read-only.

User.search_ldap has Yale phonebook hard-coded into it #653

Closed
shippy opened this issue Jul 9, 2014 · 8 comments
Closed

User.search_ldap has Yale phonebook hard-coded into it #653

shippy opened this issue Jul 9, 2014 · 8 comments

Comments

@shippy
Copy link
Contributor

shippy commented Jul 9, 2014

Status quo: whatever CAS login gets looked up in the Yale phonebook, as it's hard-coded in the method.

Expected behavior: app_setup / AppConfig should allow the user to configure their own LDAP, or skip it entirely if the institution lacks LDAP. At the very least, we should list this behavior in documentation, so that any adopter who is not Yale-based will know to change the code in their instance.

Making the code more modular is relevant to #2.

@orenyk
Copy link
Contributor

orenyk commented Jul 9, 2014

Good catch, let's definitely add this as an administrative setting. I'm wondering if it needs to be something our current admin role deals with; it seems to me like it's more of a production setting. Is it worth making some of these IT-level settings accessible to superusers via either a settings page or ActiveAdmin? We should definitely document this in our wiki either way.

@mnquintana
Copy link
Contributor

At the very least we should incorporate it into rake app:setup

@dgoerger dgoerger reopened this Jul 17, 2014
@dgoerger
Copy link
Contributor

(sorry, mouse jumped and closed this issue by mistake)

We should also per #2 consider situations in which LDAP service isn't available. Large institutions like universities are likely to have it, but we shouldn't code our app in such a way that a smaller institution can't use it. Granted, it's a fairly moot point until we enable non-CAS login in #2, because small orgs are less likely to use an industrial CAS service, but we should consider making LDAP a soft (optional) dependency of the app, part of app:setup for the webmaster to configure.

@orenyk
Copy link
Contributor

orenyk commented Aug 26, 2014

This is necessary for #399, at least an initial implementation. Moving to the Wish List for now.

@orenyk
Copy link
Contributor

orenyk commented Sep 22, 2014

This is actually critical to exporting the app, moving to 4.0.1.

@orenyk orenyk modified the milestones: Pre-Export, Wish List Sep 22, 2014
@orenyk orenyk modified the milestones: 4.0.1, Pre-Export Sep 22, 2014
@orenyk
Copy link
Contributor

orenyk commented Oct 23, 2014

Let's store the relevant parameters in an initializer / secrets.yml with Yale defaults for development and test and pulling from environment variables for production. Also, let's look at the Shifts code for how to generalize the LDAP settings.

@orenyk orenyk added this to the 4.1.0 milestone Oct 27, 2014
@orenyk orenyk removed this from the 4.0.1 milestone Oct 27, 2014
@orenyk orenyk added 1 - Ready and removed 1 - Ready labels Nov 3, 2014
@orenyk orenyk modified the milestones: 4.1.0, 4.1.1 Nov 30, 2014
@orenyk
Copy link
Contributor

orenyk commented Dec 2, 2014

I'm actually merging this into #683 since it already includes a lot of the necessary code reorganization.

@orenyk orenyk self-assigned this Dec 2, 2014
@orenyk orenyk removed the 1 - Ready label Dec 2, 2014
@orenyk
Copy link
Contributor

orenyk commented Jan 9, 2015

resolved via #1048

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants