[GH-ISSUE #121] External authentication #72

Open
opened 2026-02-28 01:20:51 +03:00 by kerem · 2 comments
Owner

Originally created by @richard-underwood on GitHub (Sep 19, 2016).
Original GitHub issue: https://github.com/tuxis-ie/nsedit/issues/121

Hi,

I could do with integrating the password authentication with AD (LDAP). Having a think about this, rather than integrating directly, it would be easy to set it up with an option to trust $_SERVER['REMOTE_USER'], effectively offloading the authentication to Apache. This would be the most flexible as Apache already has extensive authentication options.

Is this something you'd be interested in including, or should I keep this as a local modification?

Thanks.

Originally created by @richard-underwood on GitHub (Sep 19, 2016). Original GitHub issue: https://github.com/tuxis-ie/nsedit/issues/121 Hi, I could do with integrating the password authentication with AD (LDAP). Having a think about this, rather than integrating directly, it would be easy to set it up with an option to trust $_SERVER['REMOTE_USER'], effectively offloading the authentication to Apache. This would be the most flexible as Apache already has extensive authentication options. Is this something you'd be interested in including, or should I keep this as a local modification? Thanks.
Author
Owner

@tuxis-ie commented on GitHub (Sep 19, 2016):

It is far more efficient than building our own implementation. We would need to think about groups though, since that is an issue many people would want to see implemented. Any thoughts on that?

<!-- gh-comment-id:247954552 --> @tuxis-ie commented on GitHub (Sep 19, 2016): It is far more efficient than building our own implementation. We would need to think about groups though, since that is an issue many people would want to see implemented. Any thoughts on that?
Author
Owner

@richard-underwood commented on GitHub (Sep 19, 2016):

Groups would be easier with direct LDAP integration, but I'll have a think about doing it through Apache. However, I think the first step would be to implement groups without any external integration for normal installations. I can have a go at this, if you like.

One thing, though, I have no idea how WeFact fits in with groups. I'll try and take it into account, but someone who uses it would need to test that there are no conflicts.

<!-- gh-comment-id:247963624 --> @richard-underwood commented on GitHub (Sep 19, 2016): Groups would be easier with direct LDAP integration, but I'll have a think about doing it through Apache. However, I think the first step would be to implement groups without any external integration for normal installations. I can have a go at this, if you like. One thing, though, I have no idea how WeFact fits in with groups. I'll try and take it into account, but someone who uses it would need to test that there are no conflicts.
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/nsedit#72
No description provided.