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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,467,410
Community Members
 
Community Events
177
Community Groups

Crowd: hosted vs in-house

I have multiple Atlassian products, including Crowd, hosted in a data center.  Our IT will not connect Active Directory  to Crowd because it is 'out in the wild.' 

Is it possible to bring Crowd in-house and still leave the other Atlassian products in the external data center? Oh, yeah.  One more detail...Crowd has to continue to work correctly.  wink

2 answers

thank you.  I will forward this to IT and see if this will work for us.

Prior to joining Atlassian, I used Crowd for authenticating customer users to a product that operated outside of our corporate network (in another data center).  What I ended up with may meet your needs.

(1) I had an Active Directory that represented our internal user base.  This consisted of two (2) Active Directory domain controllers used by most every service internal to our company and one (1) READ-ONLY active directory domain controller setup for the purpose of this scenario.

(2) I had another LDAP directory that represented all customer-users because I needed to be sure customers and internal users were never co-mingled–a management requirement.

(3) I setup Atlassian Crowd as the bridge between the two LDAP directories and then exposed the Crowd end points to the remote data center (which I then white-listed by IP address).  A better solution would have been to use a VPN tunnel, but at the time that was not an option due to what we will just call "vendor relationship issues."

(4) Here's the important part.  Because I pinned Crowd to authenticate first against the customer LDAP then against the read-only domain controller (with no ability to resolve to the other DCs), I was pretty certain that (a) customer accounts would be resolved first (and fastest), (b) no one could update information in the Active Directory via Crowd and (c) given my Active Directory group policies that locked accounts after three (3) attempts, I was pretty certain that my corporate VPN (which was also on Active Directory) was more vulnerable than my crowd installation when it came to external attacks.

 

(Disclaimer: What I just described was done before I joined Atlassian and I'm not entirely sure if it complies with Atlassian best practices...I just know it worked.)

 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events