[GH-ISSUE #831] [INTEGRATION] Dolibarr update #296

Open
opened 2026-02-27 08:16:28 +03:00 by kerem · 3 comments
Owner

Originally created by @olaxe on GitHub (Feb 4, 2024).
Original GitHub issue: https://github.com/lldap/lldap/issues/831

Checklist

  • Check if there is already an example config for it.
  • Try to figure out the configuration values for the new service yourself.
    • You can use other example configs for inspiration.
    • If you're having trouble, you can ask on Discord or create an issue.
    • If you succeed, make sure to contribute an example configuration, or a configuration guide.
  • If you hit a block because of an unimplemented feature, create an issue.

Description of the service
Add this information to the Dolibarr service as it is buggy for the moment: https://github.com/Dolibarr/dolibarr/issues/27993

What you've tried
It is working as it is if you have only one user in the Dolibarr LLDAP group. If not, only the first user of the group will be authenticated. Other will generate error 500 and empty webpage. When your user has been replicated into Dolibarr, you can authenticate even if you have been removed from the Dolibarr LLDAP group. Sometimes, when there is an error, you will have an empty webpage and generate an error 500.

My patches to the Dolibarr code fix all of these behavior.

Originally created by @olaxe on GitHub (Feb 4, 2024). Original GitHub issue: https://github.com/lldap/lldap/issues/831 **Checklist** - [ ] Check if there is already an [example config](https://github.com/lldap/lldap/tree/main/example_configs) for it. - [ ] Try to figure out the configuration values for the new service yourself. - You can use other example configs for inspiration. - If you're having trouble, you can ask on [Discord](https://discord.gg/h5PEdRMNyP) or create an issue. - If you succeed, make sure to contribute an example configuration, or a configuration guide. - If you hit a block because of an unimplemented feature, create an issue. **Description of the service** Add this information to the Dolibarr service as it is buggy for the moment: https://github.com/Dolibarr/dolibarr/issues/27993 **What you've tried** It is working as it is if you have only one user in the Dolibarr LLDAP group. If not, only the first user of the group will be authenticated. Other will generate error 500 and empty webpage. When your user has been replicated into Dolibarr, you can authenticate even if you have been removed from the Dolibarr LLDAP group. Sometimes, when there is an error, you will have an empty webpage and generate an error 500. My patches to the Dolibarr code fix all of these behavior.
Author
Owner

@hregis commented on GitHub (Feb 4, 2024):

@olaxe i don't understand your problem with the group !

<!-- gh-comment-id:1925806937 --> @hregis commented on GitHub (Feb 4, 2024): @olaxe i don't understand your problem with the group !
Author
Owner

@olaxe commented on GitHub (Feb 5, 2024):

The problem is with the Dolibarr code. Everything is working at expected with LLDAP. I just propose an update of the Dolibarr integration to warn other LLDAP users.

<!-- gh-comment-id:1926274600 --> @olaxe commented on GitHub (Feb 5, 2024): The problem is with the Dolibarr code. Everything is working at expected with LLDAP. I just propose an update of the Dolibarr integration to warn other LLDAP users.
Author
Owner

@nitnelave commented on GitHub (Mar 12, 2024):

@olaxe since you're the one with the most context, could you send a PR with the proposed update to the dolibarr code?

<!-- gh-comment-id:1990931249 --> @nitnelave commented on GitHub (Mar 12, 2024): @olaxe since you're the one with the most context, could you send a PR with the proposed update to the dolibarr code?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/lldap-lldap#296
No description provided.