I'm looking for a part-time remote job.

Hire me


I'm the author of:

Mastering Redmine is a comprehensive guide with tips, tricks and best practices, and an easy-to-learn structure.

Check the book's project or

Buy the book

Social pages of the book:

By buying this book you also donate to Redmine (see this page).


Follow me:

Enhancement #960

Support for non-LDAP usernames

Added by Andriy Lesyuk about 9 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Major
Assignee:
Category:
Configuration
Target version:
Start date:
22 Jan 2011
Due date:
24 Feb 2011
% Done:

100%


Description

Currently Orangutan assumes that Jabber username is identical to Redmine username. It can do this way because in Softjourn we are using LDAP. But this makes Orangutan unusable outside Softjourn.

I see two methods to support non-LDAP usernames:

  1. Create a context responsible for asking Redmine username. This context (or helper context) would need also to ask password what does not seem to be good. Another way is to do like in Messenger - to create special Redmine plugin (extend current) which will generate passkey which then should be sent through Jabber.
  2. Extract Redmine username from database. Assuming Jabber ID is stored somewhere in Redmine database. We can use it to get Redmine username. If Jabber ID is not specified - user cannot use Orangutan! If Jabber ID is not currently supported in Redmine we can add such field and create special Redmine plugin (extend current) to support it.


Related issues

Related to Orangutan - Improvement #862: Support user first and last name in requests Open
Related to Orangutan - Improvement #1233: Use first name and last name instead of (or in addition to?) Jabber ID Closed 17 Nov 2010 27 Jan 2011

History

#1 Updated by Andriy Lesyuk about 9 years ago

  • Start date deleted (08 Oct 2010)

#2 Updated by Andriy Lesyuk about 9 years ago

  • Target version changed from 1.04 to 1.05

#3 Updated by Andriy Lesyuk about 9 years ago

  • Priority changed from Minor to Major

Already two external users asked me for help with Orangutan. I guess this issue becomes more critical...

#4 Updated by Andriy Lesyuk about 9 years ago

A nice suggestion from one of potential Orangutan clients...

Carmen De Vito:

The next step would then be to decouple the relationship between LDAP and IM names. Maybe we can perform IM username lookups via a custom field or with the user’s email address.

#5 Updated by Andriy Lesyuk almost 9 years ago

Some kind of checklist:
  • Store redmine user login in Orangutan::User as new member login [DONE];
  • Use special function GetLogin to fetch Redmine user login when comparing (search for $user->GetJabberUserID) [DONE];
  • Use special function (e.g. Orangutan::User::GetDisplayName) to display just login, first and last name or JID (use login@hostname if jabber field1 is disabled) instead of login@hostname (search for $main::config->Get('jabber', 'hostname')) [DONE].

1 New special field holding user’s Jabber ID is to be called jabber.

#6 Updated by Andriy Lesyuk almost 9 years ago

  • Start date set to 22 Jan 2011
  • Status changed from Open to In Progress

#7 Updated by Andriy Lesyuk almost 9 years ago

  • % Done changed from 0 to 30

#8 Updated by Andriy Lesyuk almost 9 years ago

  • % Done changed from 30 to 60

#9 Updated by Andriy Lesyuk almost 9 years ago

Done everything mentioned above!.. But some new issues appeared:
  • Should check all occurances of GetUser() function and possibly replace with GetUserLogin() [DONE];
  • When in requests username does not contain @hostname Orangutan adds hostname by itself - should assume that this is login (right?)! All such places marked with FIXME;
  • Should also check all occurances of UserExists;
  • Check all places where login is used (mostly in Orangutan::Query).

#10 Updated by Andriy Lesyuk almost 9 years ago

Done everything mentioned above!.. But some new issues appeared:
  • Should check all occurances of GetUser() function and possibly replace with GetUserLogin() [DONE];
  • When in requests username does not contain @hostname Orangutan adds hostname by itself - should assume that this is login (right?)! All such places marked with FIXME [DONE];
  • Should also check all occurances of UserExists [DONE];
  • Check all places where login is used (only Orangutan::Query left) [DONE];
  • Fix all FIXMEs (this way I marked potential problems)...

P.S. Weird... But I could not update above note!..

#11 Updated by Andriy Lesyuk almost 9 years ago

  • % Done changed from 60 to 100

Seems to be done... But how to test?!..

#12 Updated by Andriy Lesyuk almost 9 years ago

  • Status changed from In Progress to Closed

#13 Updated by Andriy Lesyuk almost 9 years ago

  • Due date set to 24 Feb 2011

Also available in: Atom PDF

Terms of use | Privacy policy