Iteration 4 Feature: Identity

Hi, sending identity user stories we put together with Martyn. As a user I should be able to share identity in Conductor and katello * Check up on Katello see whether it uses Warden or OmniAuth and what the situation is re: migrating to OmniAuth if not already there * Use same authentication framework in Conductor and Katello (either OmniAuth or Warden) depending on above result, this framework should support Active Directory and SSO * add rpms dependencies to Conductor * implment SSO for Conductor and Katello As an admin I should have running identity server after installing Conductor * In aeolus-configure point conductor to existing AD server or set up own identity server (LDAP?) if no AD is available As an admin I should be able to create local users for Conductor (Conductor local users doesn't need to have access to Katello) * check up on Katello and do it same way - it probably already supports this, if it doesn't then steps are: * when authenticating a user, first authenticate against local db * if the user is not found in local db, authenticate against LDAP * if auth is successful, create this user in local conductor DB too, but without password so user has to be authenticated always against LDAP * add some flag to distinguish between local/no-local users in user listing * allow editing only some settings (quota) for no-local users Jan