Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Crowd posixAccount read-write

Hi all.

I'm trying to integrate my Crowd with OpenLDAP.

My LDAP server is used for user login on some servers. As such, the objectClass is posixAccount. It is my understanding that Crowd can only handle posixAccount as read-only.

I have 2 questions:

1. Why?

2. Does anyone have some recommandations about how to setup crowd with a different objectClass that would work as user login for the servers and eventually how to define a different class in the LDAP client - aka change the setup of the clients?

5 answers

I am also interested in the questions of these answers !!

I agree with __geo__. If Crowd supports posixAccount and posixGroup directly, we can manage openLDAP with Crowd.

Would be nice to have someone from Atlassian answer this. Would it be possible?

Any news from Atlassian side about this topic?

We have the same situation. We fist setup a crowd and LDAP (without posix). Everything works fine. Now we want to include our Linux Servers for authentication and need the additional posixAccount objectclass. Read-only is no option for us because we want that everyone is able to reset their password in Crowd and we using the nested group functionality from crowd for all our applications.

 

We tried to have 2 LDAP Servers (1 posix and 1 non-posix that is connected to Crowd). We didn't found a proper possibility to sync both OpenLDAP Servers. So the easiest and most efficient solution would be to have one LDAP Server with posix that is connected with crowd (read-write).

Sorry Nathalie. No updates from Atlassian on this.

What I did was to allow password updates only on LDAP. This works fine even if it restricts the possibilities.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

221 views 7 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you