Thanks for verifiying! On Tue, Mar 15, 2016 at 2:59 PM, Oleg Palij <o.pa...@dp.uz.gov.ua> wrote:
> In 3.1.1 snapshot #171 ldap users were imported correctly. > > 15 марта 2016 г., в 08:35, Maxim Solodovnik <solomax...@gmail.com> > написал(а): > > was reported in JIRA as > https://issues.apache.org/jira/browse/OPENMEETINGS-1348 > should be fixed > can be verified using build #171+ > https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%203.1.x/171/ > > could you please verify it works for you as expected? > > > On Mon, Mar 14, 2016 at 3:34 PM, Maxim Solodovnik <solomax...@gmail.com> > wrote: > >> produced backup file was successfully imported into 3.1.0RC1 >> User types were created as expected >> LDAP users are able to login (no extra users are created) >> >> Backup/restore is one of key functions in Apache OpenMeetings, could you >> please provide more detailed steps to reproduce (example backup file) >> so we can investigate and fix any possible issue? >> >> On Mon, Mar 14, 2016 at 3:20 PM, Maxim Solodovnik <solomax...@gmail.com> >> wrote: >> >>> quick check of 3.0.7 shows >>> >>> 1) users created using LDAP login are being created with type='ldap' in >>> the system >>> 2) users with type ldap are exported with correct type and domain_id >>> >>> going to check import >>> >>> On Mon, Mar 14, 2016 at 2:54 PM, Maxim Solodovnik <solomax...@gmail.com> >>> wrote: >>> >>>> could you please (privately) provide example backup demonstration the >>>> issue? >>>> this will speed up fixing >>>> meanwhile I'll try to reproduce it locally >>>> >>>> On Mon, Mar 14, 2016 at 2:43 PM, Oleg Palij <o.pa...@dp.uz.gov.ua> >>>> wrote: >>>> >>>>> Hello! >>>>> >>>>> Initially I have upgraded from* 2.1.0 to 3.0.7.* >>>>> In 2.1.0 ldap user record looks like: >>>>> >>>>> | id | activatehash | age | >>>>> availible | deleted | externalUserId | externalUserType | firstname | >>>>> forceTimeZoneCheck | language_id | lastlogin | lastname | lasttrans | >>>>> level_id | login | password | >>>>> pictureuri | regdate | resethash | salutations_id | sendSMS | >>>>> show_contact_data | show_contact_data_to_contacts | starttime | >>>>> status | updatetime | user_offers | user_searchs | adresses_id | >>>>> omtimezoneId | sip_user_id | >>>>> | 6 | d61cc7a3f1efefd03aaaa17292f967d0 | 2011-10-05 00:00:00 | >>>>> 0 | | NULL | LDAP | Олег | >>>>> | 9 | NULL | Палій | 0 | 3 | >>>>> o.pa...@example.com | eereiciroophaiGheiWa9ohshuG4eefe | | >>>>> 2011-10-05 13:19:46 | NULL | 1 | | >>>>> | | 2013-05-08 14:55:15 | 1 | >>>>> 2016-03-11 10:06:42 | | | 6 | >>>>> 20 | NULL | >>>>> >>>>> >>>>> >>>>> After importing 2.1.0 backup to 3.0.7, ldap user record looks like: >>>>> >>>>> | id | activatehash | age | >>>>> deleted | domain_id | externalUserId | externalUserType | firstname | >>>>> forceTimeZoneCheck | language_id | lastlogin | lastname | lasttrans | >>>>> login | owner_id | password | >>>>> pictureuri | regdate | resethash | salutations_id | sendSMS | >>>>> show_contact_data | show_contact_data_to_contacts | starttime | >>>>> time_zone_id | type | updatetime | user_offers | user_searchs | >>>>> adresses_id | sip_user_id | >>>>> >>>>> +----+----------------------------------+---------------------+---------+-----------+----------------+------------------+-----------+--------------------+-------------+-----------+------------+-----------+----------------------+----------+----------------------------------+------------+---------------------+-----------+----------------+---------+-------------------+-------------------------------+---------------------+--------------+----------+------------+-------------+--------------+-------------+-------------+ >>>>> | 6 | d61cc7a3f1efefd03aaaa17292f967d0 | 2011-10-05 00:00:00 | >>>>> | NULL | NULL | LDAP | Олег | >>>>> | 9 | NULL | Палій | 0 | >>>>> o.pa...@example.com | NULL | eereiciroophaiGheiWa9ohshuG4eefe | >>>>> NULL | 2011-10-05 13:19:46 | NULL | 1 | | >>>>> | | 2016-03-14 09:39:37 | >>>>> Africa/Cairo | external | NULL | NULL | NULL | >>>>> 6 | NULL | >>>>> >>>>> New fields 'type' were inserted with a value 'external' and >>>>> 'domain_id' with NULL value. >>>>> And for every logged in user openmeetings creates new record in >>>>> database. >>>>> So I have to do: >>>>> update om_user set domain_id=1,type="ldap" where type="external"; >>>>> After that every thing back to normal. >>>>> >>>>> >>>>> >>>>> Then I upgraded from* 3.0.7 to 3.1.0-rc1.* >>>>> After importing 3.0.7 backup to 3.1.0 ldap user record looks like: >>>>> >>>>> | id | activatehash | age | >>>>> deleted | domain_id | external_id | external_type | firstname | >>>>> forceTimeZoneCheck | inserted | language_id | lastlogin | >>>>> lastname | lasttrans | login | owner_id | password >>>>> | pictureuri | regdate | resethash | >>>>> salutation >>>>> | sendSMS | show_contact_data | show_contact_data_to_contacts | >>>>> time_zone_id | type | updated | user_offers | user_searchs | >>>>> address_id >>>>> | sip_user_id | >>>>> >>>>> +----+----------------------------------+---------------------+---------+-----------+-------------+---------------+-----------+--------------------+---------------------+-------------+-----------+------------+-----------+----------------------+----------+----------------------------------+------------+---------------------+-----------+------------+---------+-------------------+-------------------------------+--------------+----------+---------+-------------+--------------+------------+-------------+ >>>>> | 6 | d61cc7a3f1efefd03aaaa17292f967d0 | 2011-10-05 00:00:00 | >>>>> | 1 | NULL | LDAP | Олег | >>>>> | 2016-03-14 09:47:16 | 9 | NULL | Палій | 0 >>>>> | >>>>> o.pa...@example.com | NULL | eereiciroophaiGheiWa9ohshuG4eefe | >>>>> NULL | 2011-10-05 13:19:46 | NULL | mr | | >>>>> | | Etc/GMT+2 | external | >>>>> NULL >>>>> | NULL | NULL | 6 | NULL | >>>>> >>>>> 'type' again become 'external'. With new field 'external_type' set to >>>>> 'LDAP', but 'external_id' is NULL. 'domain_id' was preserved. >>>>> >>>>> >>>>> >>>>> When I logged in with this user, openmeetings creates new record: >>>>> >>>>> | 84 | NULL | 2016-03-14 09:49:05 | >>>>> | 1 | NULL | NULL | Олег | >>>>> | 2016-03-14 09:49:05 | 9 | NULL | Палій | NULL >>>>> | >>>>> NULL | NULL | xoof3co4athooqu7shieph3Aesaitoh9 | NULL >>>>> | 2016-03-14 09:49:05 | NULL | mr | | >>>>> | | Etc/GMT+2 | ldap | NULL | >>>>> NULL | NULL | 84 | NULL | >>>>> with NULL login, external_id, external_type. And with 'ldap' in >>>>> 'type' field. >>>>> >>>>> And every time I am logging in with this user, openmeetings creates >>>>> new same field in database over and over again (incrementing id of >>>>> course). >>>>> So any user permissions and accesses can't be applied. >>>>> >>>> >>>> >>>> >>>> -- >>>> WBR >>>> Maxim aka solomax >>>> >>> >>> >>> >>> -- >>> WBR >>> Maxim aka solomax >>> >> >> >> >> -- >> WBR >> Maxim aka solomax >> > > > > -- > WBR > Maxim aka solomax > > > -- WBR Maxim aka solomax
