Forum

Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.

No user created fro...
 
Notifications
Clear all

No user created from LDAP

8 Posts
2 Users
0 Reactions
3,038 Views
(@dinf_udes)
Posts: 11
Active Member
Topic starter
 
[#8710]

Hello,
Since we migrate to the latest version (10.2.1), new users who log in with ldap do not create the new user, nor resource/contact. The user can however access Projeqtor, but doesn't see anything. After checking the code, the problem is that authentication method do a rollback on the BD thus removing the newly created user. The erreur is that it doesn't have access to create Resource. However, the authenticate method do not return an error if a rollback occur, thus allowing the user to log in, but without a real user. 

I have add trace log in authenticate method and save method of UserMain, ResourceMain and this is a result :----- DEBUG ----- User->authenticate('userID', 'password')
----- DEBUG ----- User->authenticate : access through LDAP
----- DEBUG ----- User->authenticate : LDAP authenticate
===== TRACE ===== User->save - Parent save : Utilisateur #492 inséré
===== TRACE ===== User->save - Erreur save ressource : Contrôles invalides.

Vous n'avez pas le droit de mettre à jour cet élément (Ressource #492)
===== TRACE ===== authenticate - Rollback user creation : Contrôles invalides.

Vous n'avez pas le droit de mettre à jour cet élément (Ressource #492)
===== TRACE ===== User->save - Parent save : L'élément Utilisateur #492 n'a pas été trouvé dans la base de données.

Is there a new configuration to adjust following the update?
Thanks!


 
Posted : 17 Jan 2023 18H16
(@babynus)
Posts: 14952
Member Admin
 

Hi,
Thanks for your detailed explanation.
This helped me find the issue and fix it.
To fix, add one line after line 1406 in projeqtor/model/UserMain.php :

    public function authenticate( $paramlogin, $parampassword) {
      SqlElement::$_cancelRecursiveControl=true;

​​​​​​​This fix will be included in patch V10.2.2


 
Posted : 17 Jan 2023 19H27
(@dinf_udes)
Posts: 11
Active Member
Topic starter
 

Hello,
Thanks for the fix. It works.
As an administrator however, I cannot change the common name of the user as before. I can only change the initials on the user. Maybe it is related to my other post? The access seem to be broken. Does this recursiveControl check be related?
Thanks again!


 
Posted : 17 Jan 2023 19H39
(@babynus)
Posts: 14952
Member Admin
 
As an administrator however, I cannot change the common name of the user as before. I can only change the initials on the user.

What message do you get ?
Do you have errors in the log file ?

Maybe it is related to my other post? The access seem to be broken. Does this recursiveControl check be related?

Possible, no sure.


 
Posted : 17 Jan 2023 20H10
(@babynus)
Posts: 14952
Member Admin
 

I just tested and could not reproduce the issue.


 
Posted : 17 Jan 2023 20H12
(@dinf_udes)
Posts: 11
Active Member
Topic starter
 

The field is just greyd and I cannot modify the content. No errors in the log...


 
Posted : 17 Jan 2023 20H16
(@babynus)
Posts: 14952
Member Admin
 

Any screen customization ?


 
Posted : 19 Jan 2023 20H47
(@dinf_udes)
Posts: 11
Active Member
Topic starter
 

Not that I'm aware of.


 
Posted : 19 Jan 2023 20H58
Share:

Scroll to Top