•  
     
    story #8528 create nonexistant user account at import time
Summary
site admin
create nonexistant user account at import time
I keep history of changes (changeset, assigned to) instead of having random / anonymous comments

This first step is meant to allow creation of accounts, the management of account desactivation is done in story #8545.

In this first step, accounts will be create but will have ACTIVE status (hence it's not meant to be used in production).

The proposal is to deal with user accounts before and after the import process:

  • At export time, the export tool create a "users.xml" file along project.xml in archive, this file contains informations about users exported
    • Informations gathered
      • LdapID
      • username
      • real name
      • email
    • This list is built as a post processing of project.xml
  • At import time
    • add a new temporary option --force-create-all-users-active
    • if this option is used, compute and display the list of user accounts that need to be created and/or activated
    • if accepted (admin type Yes in console) user accounts are created (or activated if already existing) with random password (so user cannot login)
    • The import process is done as usual
    • no email is sent to "temporary" users.
Nouha Terzi (terzino), Salma MOAKHAR (moakhars), Denis PILAT (denis_pilat)
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Flow chart in attachment describes how we detect users in archive in order to import them (or to generate a mapping file).
Details
#8528
Manuel Vacelet (vaceletm)
2015-11-27 12:27
2015-10-28 12:02
8615

References

Follow-ups

User avatar

Hi Salma, Nouha, Denis,

During development of this story, we faced some difficulties with the way we are detecting who should be created/activated/… It appears that site admin may have to provide a mapping file in order to ease the import of users.

This is notably the case when a user in the import archive may match some users (same email address but different username for example). This means that site admin who wants to import a project needs to generate the mapping file beforehand (thanks to a script we will provide, based on the attached flowchart).

The format of the file will be CSV:

name,action
nterray,create
yrossetto,activate
sandrae,map:sechinard

It means that the scope of this story goes beyond the initial study.

How do you feel about this?


  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Attachments story-8528-detect-users-flowchart.jpg added
  • Technical informations
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
Split the story in 2, see art #8545

  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
Salma, Nouha, Denis,

What do you think about this proposal ?

  • CC list set to Salma MOAKHAR (moakhars), Nouha Terzi (terzino), Denis PILAT (denis_pilat)