Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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
LuizA Rising Star Dec 25, 2012

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.



0 votes

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

Atlassian Community Events