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

Your Points Tracker
  • 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
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?
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 and Google usernames

The documentation for Crowd's Google Apps connector states:

"Usernames must exist in Google Apps as well as Crowd and a person's username must be the same in both Google Apps and Crowd. The Crowd Google Apps connector does not support the automatic adding of users. If a user exists in Crowd but not in Google Apps, then the user will not be able to log in to Google Apps."

If I export from Google a list of my accounts, the CSV file has a column labelled "account_name" where the values are

For Crowd, do I make the cn equal to firstname.lastname only or do I make it equal to

It may be pertinent to state that this is Google Apps for Business, and is my managed domain.


2 answers

1 accepted

0 votes
Answer accepted

Hello Philip,

If your username in Google Apps is "" (I mean, if this is the username that you use to login into the Google Apps) so the cn for Crowd needs to be "". I hope this helps.



Hi Luiz

Thank you for this.

Since I am also using LDAP for server logins, the current server configuration won't support full usernames but will work with the bit before the @. This would suggest that I need to have two "cn" entries per user - one with just firstname.lastname and one with

That is quite an administrative overhead and a potential risk of typing mistakes.

Is there any way to get Crowd's Google/SSO implementation to strip or add the bit after "@" so that I only need one cn entry?



I've now realised that Unix logins will check against the uid attribute so I don't need two cn entries. This means that cn can be and uid can just be firstname.lastname.

I've also "discovered" LDAP Account Manager which makes maintaining the underlying LDAP entries a breeze.

Suggest an answer

Log in or Sign up to answer
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...

180 views 6 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