|
Thanks for the prompt attention to the issue.
Given your experience of having the macros work in your clean 2.8.0 installation, I'll try the macros in another Confluence 2.8.0 installation I manage and report back. One notable difference between that installation, and the one I use at work, is that the work 2.8.0 is configured for external user management in Active Directory, which may not have anything to do with the issue, but I have not basis to guess one way or the other. Hmm. It is possible that using external user management in Active Directory could be affecting it. Unfortunately that is not something I can test on my personal instance. We are using Active Directory/LDAP for user management at my workplace, but we are still running Confluence 2.7.3. I will contact the network folks at work to find out about getting a test box setup with Confluence 2.8, as we should probably start testing the latest version anyway for a future upgrade
Out of curiosity, could you answer these two questions: 1. Based on your reply, I am guessing you are using AD/LDAP for user and group management as mentioned here: http://confluence.atlassian.com/display/DOC/Add+LDAP+Integration 2. The mention of the term "External User Management" made me wonder if perhaps you have External User Management enabled in the Administration Console for Confluence (more info found here: http://confluence.atlassian.com/display/DOC/Activating+External+User+Management My bad – the use of the phrase "external user management" was misleading.
No, I don't have external user management turned on. Yes, I have directly integrated Confluence with AD by customizing the atlassian-user.xml file, and I did read the referenced articles many times before and during the process of moving to Confluence to AD, but the process was still fragile and finnicky, which isn't a knock against Confluence, it's just the nature of the beast. No, I'm not using any software to intermediate the user authentication, such as Crowd. All of the user accounts in AD, and all of the groups, are exposed into Confluence dynamically, such that Confluence doesn't have more than one or two local user accounts and groups. When I browse users or groups in Confluence, I see a list of users and groups that are fetched by Confluence from AD. I tested the plugin on my other Confluence installation, which is comprised only of local users and groups and has no integration with a directory server, and the plugin worked swimmingly. Let me know if there's anything else I can do to help debug it, like a debug build that produces more log information etc. Updated name for clarification
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
In Progress
Major
When using LDAP, macros render as NullPointerException in Confluence 2.8.0
Thank you for alerting me to this issue. Unfortunately, the Page Access Macros plugin does not support Confluence 2.8 as of yet. I will be testing the plugin on the latest version soon, and will keep alert for this issue during testing. The next release will definitely support Confluence 2.8.