You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Setting up LDAP in Crowd for authentication only but "User Group Attribute" is required by setup screen. Our LDAP schema doesn't seem to have memberOf attribute and we wouldn't be using it anyway.
Is there anyway to work around this?
It looks like you have a Posix based LDAP schema, could you try using one of the Posix based LDAP configurations in Crowd.
Also make sure that you have the "Use the User Membership Attribute" un-ticked on the Connector tab. Here is the specific documentation related to OpenLDAP directories that have a Posix Schema.
Crowd also has a more generic, Posix Schema configuration:
Could you please try to use "dummyValue" into your "User Group Attribute" field and ensure that "Group Members Attribute" is valid.
This would force Crowd to use the membership mapped by the groups instead of LDAP users. Please try the above suggestion and let us know how it goes.
As mentioned earlier, if the mapping of the membership is configured under the groups, you should be able to configure it here, and using "DummyValue" as the "User Group Attribute" value would force Crowd to use only this parameter to retrieve all the necessary membership from your LDAP server.
Hope it helps.
Here is the schema for users:
description: user accounts
I hadn't initially planned to use groups since I am using Delegated Authentication Directory seutp but pulling users out of a specific group will be helpful.
As mentioend on the previous response, if you put "dummyValue" into your "User Group Attribute" field and "memberuid" into your "Group Members Attribute" field. Crowd would ignore the "dummyvalue" process the membership using the configured "Group Member Attribute".
Could you please try the mentioned suggestion and see if it helps.
Sorry to hear that, logs might be able to help us here but we would need to analyze it and understand the whole configuration.
It would be best if we continue our troubleshooting process trough https://support.atlassian.com/ so that we could see your configuration and logs confidentially.
If it is okay with you, you could attach the screenshot of your detailed configuration here and please let me know the directory type (connector/delegation) you used on your system.