[MGNLLDAP-117] Pulse requires re-login to display a publication request for LDAP user Created: 06/Nov/17 Updated: 11/May/18 Resolved: 12/Mar/18 |
|
| Status: | Closed |
| Project: | LDAP Connector |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.10, 1.9.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Ewa Snopczynska-Sienczylo | Assignee: | Milan Divilek |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Date of First Response: | |||||||||
| Sprint: | Kromeriz 133, Kromeriz 135, Kromeriz 136, Kromeriz 137, Kromeriz 138 | ||||||||
| Story Points: | 8 | ||||||||
| Description |
| Comments |
| Comment by Bret Lederle [ 19/Dec/17 ] |
|
Recently upgraded from 5.5.3 to 5.5.7 and am now experiencing this issue as all our users login with LDAP. |
| Comment by Ervin Vystup [ 20/Dec/17 ] |
|
Hi esienczylo, could you please specify on which version it occurs? Was that also on 5.5.7 how blederle mentioned? Thank you in advance for the info |
| Comment by Ervin Vystup [ 20/Dec/17 ] |
|
I was able to reproduce the issue on 5.5.7 and also found out one more strange thing. More info added to the description of the ticket. |
| Comment by Milan Divilek [ 05/Feb/18 ] |
|
This issue is caused by wrong configuration in ldap/ad.properties. With correct ldap/ad.properties configuration pulse is correctly updated also for LDAP/AD users There are two ways how user is resolved This method is used when user is logging into Magnolia and is also used for initialization of pulse and pulse counter after login. Configuration for this part is ok. 2. We know group name -> info.magnolia.cms.security.UserManager#getUsersWithGroup(String groupName) This is used for update pulse and pulse counter and this doesn't work correctly. Most often caused by missing groupMembershipAttribute property in ldap/ad.properties file |
| Comment by Bret Lederle [ 05/Feb/18 ] |
|
I just verified that I have the groupMembershipAttribute. I was able to find something else that explained this behavior. For an AD username that is BR1234, I can successfully login to Magnolia as 'br1234' and 'BR1234'. When logging in with lowercase, I do not get pulse notifications. And when logging in with the letters in CAPS, I do get the notifications. I feel that if i can successfully login with either, then the notifications should show up with either. |
| Comment by Milan Divilek [ 06/Feb/18 ] |
|
Hi Bret, |
| Comment by Bret Lederle [ 06/Feb/18 ] |
|
Great, thanks. Let me know if you need me to test anything or provide more details. |