Branch/Tag 가 지정되어 있지 않습니다.
paginate-search-init
main
s3
fix-delete-user
timeline-cli
blog-title
signature
remove-dup-images
ldap-non-anon
drone-ci
DearRude/force-lang
igalic/go/async-all-mut
go/async
floreal/translations-update
missing-docs
RAOF/fix-arm64-build
epsilon-phase/authorized-fetch
upgrade
improve-the-editor-once-again
igalic/feat/custom-fairing-domains
feature/ldap
test/dotenv_error
fix-mobile-margin
0.7.2
0.7.0
0.2.0-alpha-1
0.3.0-alpha-2
0.4.0-alpha-4
0.5.0
0.6.0
0.7.1
레이블
레이블 초기화
Related to the REST API
Code running on the server
Stuff related to Federation
Related to the front-end
Translations, and related code
More about project management or code than the project itself
The building, or installation process of Plume
Something isn't working
We need to talk
New feature or request
This is a new feature
Compatibility with different browsers, readers and OS
Related to an external package that Plume uses
UI/UX related issues and PRs
Good for newcomers
Extra attention is needed
Issues affecting only mobile UX
How elements're rendered out for the end user
Something else needs to be fixed first
This issue or pull request already exists
This PR is not complete yet
Issues concern a limited number of instances
This doesn't seem right
Need to be discussed by the community (on Loomio)
This PR is ready to be reviewed
Proposed ideas worth considering
This is issue has been created after a vote on Loomio
This will not be worked on
Apply labels
A: API
Related to the REST API
A: Backend
Code running on the server
A: Federation
Stuff related to Federation
A: Front-End
Related to the front-end
A: I18N
Translations, and related code
A: Meta
More about project management or code than the project itself
A: Security
Build
The building, or installation process of Plume
C: Bug
Something isn't working
C: Discussion
We need to talk
C: Enhancement
New feature or request
C: Feature
This is a new feature
Compatibility
Compatibility with different browsers, readers and OS
Dependency
Related to an external package that Plume uses
Design
UI/UX related issues and PRs
Documentation
Good first issue
Good for newcomers
Help welcome
Extra attention is needed
Mobile
Issues affecting only mobile UX
Rendering
How elements're rendered out for the end user
S: Blocked
Something else needs to be fixed first
S: Duplicate
This issue or pull request already exists
S: Incomplete
This PR is not complete yet
S: Instance specific
Issues concern a limited number of instances
S: Invalid
This doesn't seem right
S: Needs Voting/Discussion
Need to be discussed by the community (on Loomio)
S: Ready for review
This PR is ready to be reviewed
Suggestion
Proposed ideas worth considering
S: Voted on Loomio
This is issue has been created after a vote on Loomio
S: Wontfix
This will not be worked on
레이블 없음
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
마일스톤
Set milestone
마일스톤 초기화
No items
마일스톤 없음
담당자
Assign users
담당자 초기화
담당자 없음
참여자 3명
알림
마감일
기한이 올바르지 않거나 범위를 벗어났습니다. 'yyyy-mm-dd'형식을 사용해주십시오.
마감일이 설정되지 않았습니다.
의존성
No dependencies set.
Reference: Plume/Plume#902
Reference in New Issue
아직 콘텐츠가 없습니다.
'%!s(<nil>)' 브랜치 삭제
Deleting a branch is permanent. It CANNOT be undone. Continue?
아니오
예
Is it possible to use a (read only) ldap bind user instead of anonymous bind?
@trinity-1686a Do you have any idea?
I'm not sure what you mean, I'm not very familiar with ldap (despite implementing support in Plume), from what the internet seems to say, an anonymous bind is a bind with empty DN/password, which Plume is not doing (DN is computed from config and username, password is, well the user password).
If the 5
LDAP_*
environment variables don't provide what you need, it's probably not implemented, and I'd welcome any ressource explaining better your request.Hi @trinity-1686a,
I'm also not familiar with ldap. I configured Jitsi with ldap and a bind user. Take a look at jitsi ldap configuration and LDAP_BINDDN / LDAP_BINDPW:
https://github.com/jitsi/docker-jitsi-meet/blob/master/env.example#L161
I guess it first bind that user, then bind a 2nd time with the right user? In a few days once I'll have time I'll make a WIP pr, would you be able to test it?
Yes, I'll test it. I'd like to setup plume with ldap and bind user.
Binddn user is a read only ldap user to authenticate and than check the right user credentials. I use it with search filter to check group membership ("memberof"). Could you try similar config as jitsi? Search filter with binddn should be most flexible?