youngmon/atlassian-qna huggingface dataset:
Atlassian sites say "We are currently experiencing difficulties." but status page says no problems
Asked by John Price:

Has anyone else experienced this? Pretty frequently I cannot get to the Atlassian Confluence documentation for their apps and get the error message above. But the [](http://status.atlassian.com/ "status page")<http://status.atlassian.com/>always says All Systems Operational, and zero Past Incidents.

I'm in the US (East Coast) and a tracert to [confluence.atlassian.com](http://confluence.atlassian.com)shows no problems.


Answers:
author: BlackKiteTechnology
body: @Typoheads- Does anyone at Atlassian actually read these pages? I've tried tweeting to them but no response there either.

comments: author: Nic Brough -Adaptavist-
body: Yes and no - this is a user community. Atlassian are here, and they do read stuff, and they do post. But there's nothing formal to say they have to respond to anything here at all. They often do, but they don't have to.

I know they do see stuff being talked about here and take it into their internal discussions as well, but again, it's totally informal.

I'd raise an issue with them at [jira.atlassian.com](http://jira.atlassian.com)- that way you'll at least get some response, even if it's just an apology


author: BlackKiteTechnology
body: I am having the exact same problem and I am based in London. I am evaluating their products and it is really starting to annoy me that I cannot access their documentation.


author: Thomas
body: This has been the issue the past week. I've tried opening a release note page from a previous version and it took me over 50 reloads to actually load the whole page as it should look like, and all the images are loaded.

This is becoming really annoying if you are looking for some info on the site.

If this is the way they are promoting their own product on the market and the provide info for future customers, good luck with gaining new ones.


author: btokarchuk
body: I have the exact same problem and am on the west coast (SF Bay Area). This problem has been going on for weeks and I finally decided to come and see if there was anything on this site about it.


Tags: network
TeamCity Crowd Plugin
Asked by Greg Gigon:

Hi guys

Not a question really, just to let you know that I've created a TeamCity Crowd plugin. Makes it possible for TeamCity to Authenticate users via Crowd. Useful where Crowd is being used for User management with other tools (JIRA, Confluence, Stash, etc.).

Short blog post:

[](http://greggigon.com/2014/02/05/new-teamcity-plugin-for-user-authentication-via-atlassian-crowd/)<http://greggigon.com/2014/02/05/new-teamcity-plugin-for-user-authentication-via-atlassian-crowd/>

GitHub repo:

[](https://github.com/greggigon/TeamCity-Crowd-Plugin)<https://github.com/greggigon/TeamCity-Crowd-Plugin>

Greg


Answers:
author: Caspar Krieger
body: JIRA can't have new applications (it's limited to just the 1 "Crowd application"), but you should be able to expose that application. Follow the JIRA-side instructions for connecting Confluence to JIRA: <https://confluence.atlassian.com/display/DOC/Connecting+to+Crowd+or+JIRA+for+User+Management#ConnectingtoCrowdorJIRAforUserManagement-ConnectingConfluencetoJIRAforUserManagement>


author: Greg Gigon
body: I don't know, I never tested this with Jira embedded Crowd (wasn't aware there is such thing).Give it a try and let us know. If there is a way to add Application to Jira-Crowd then it should work.


author: Edward Dumser
body: Does it work with JIRA-embedded Crowd?


author: Caspar Krieger
body: Nice! Thanks for the heads up :)


Tags: app

crowd-administration

teamcity
How do I enable new users in Crowd to access Jira, Stash, etc.
Asked by Ethan Trewhitt:

I have set up evaluation versions of Crowd, Jira, Stash, and Confluence. Everything seems well and good between the services for my user account, which I've been using for testing. Crowd connects to LDAP correctly, and the other three services use Crowd's SSO to manage users. Where I get a bit lost is in allowing new users (who have valid LDAP credentials) to access the services.

I have Crowd set to add new users to confluence-users, stash-users, and jira-users as soon as they log in for the first time.

The first time user BOB1 visits Stash, he logs in, and Crowd verifies his credentials. When Crowd sends him back to Stash, Stash says "You do not have permission to access Stash". Apparently this is because Stash's view of the Crowd directory is out of date (by more than a few seconds) and hasn't been updated to reflect that Crowd has just added BOB1 to stash-users. Once I go into Stash and tell it to update the Crowd directory, BOB1 can then log in, but a manual update is obviously not the solution.

What is the proper way to allow each user to access the services as soon as they log in for the first time? Thanks in advance.


Answers:
author: Caspar Krieger
body: Unfortunately the only solution currently is to wait for the automatic synchronization to be triggered for each application connected to Crowd. You can make this less painful by decreasing this interval to a low number (like a few minutes) for each of the applications.

Please vote on [CWD-2650](https://jira.atlassian.com/browse/CWD-2650) if you'd like this to be fixed.

comments: author: Ethan Trewhitt
body: Caspar - thanks for the reply. I voted on the bug but I worry that it's been around for a while and is still unresolved. This is a pretty glaring bug that will cause every new user to get an error on their first login attempt with no visible expectation that the error will resolve itself in the future.  

I recently sent out an email suggesting that several folks try out the services I just set up. The result of this bug is that every new user is going to try, and fail, to log in ... this will be their first experience trying out our Atlassian servers and it will leave a bad taste in their mouths. It's going to be hard to convince my company to buy these servers if every new user sees such an obnoxious bug.

I'm willing to try a workaround if one exists. What if I add everyone on the LDAP server to the stash-users group? Would there be any downside to that?


author: Caspar Krieger
body: Pre-adding your users to the confluence-users, jira-users, and stash-users groups in the LDAP directory (or in Crowd) would prevent the specific case of the error you're seeing, and there shouldn't be a downside to that as far as Crowd is concerned.

Don't forget to drop the synchronization interval on each of the applications as well.


Tags: crowd-administration
Upgrading JIRA 4.0.1 , Confluence 3.1 , Crowd 2.0.3 and Postgres 8.4 to latest versions
Asked by Peter Atthem:

Hi,

Am doing an upgrade on JIRA 4.0.1 to 6.1.7, Confluence to 5.4.2, Crowd to 2.7 and Postgres to 9.2.

Is there any compatibility matrix and suggestion where to start.

For JIRA, I know I need to go to 4.4.5 before I go to 6.

Should I start with crowd and make sure all looks good before doing the other applications?

And if I upgrade crowd to latest, will the orther applications still work?

Feels like a bit much to do in a big bang.

Thanks

Peter


Answers:
author: Peter Atthem
body: Hi,

Thanks Svante.

Here is the steps I took and it worked good.

Step 1. Upgrade Crowd to 2.1.1 due to JIRA 4.0.1 and confluence compatabilitlty. {#toc-hId-1673423649}
------------------------------------------------------------------------------------------------------

Step 2. Upgrade from JIRA 4.0.0.1 to 4.4.5 {#toc-hId--878733312}
----------------------------------------------------------------

Step 3. Upgrade Crowd to 2.7 {#toc-hId-864077023}
-------------------------------------------------

Step 4. Upgrade JIRA to 6.1.7 {#toc-hId--1688079938}
----------------------------------------------------

Step 5. Upgrade Confluence to 3.5.17 {#toc-hId-54730397}
--------------------------------------------------------

Step 6. Upgrade Confluence to 4.3.7 {#toc-hId-1797540732}
---------------------------------------------------------

Step 7. Upgrade Confluence to 5.4 {#toc-hId--754616229}
-------------------------------------------------------

Steg 9. Upgrade Postgres 8.4 to 9.0 {#toc-hId-988194106}
--------------------------------------------------------

I took lots of steps due to major changes in JIRA and Confluence in earlier versions.

Might have been a bit over safe to do all steps, but it worked and we are happy =)

BR

Peter


author: Svante Gustafsson Bj?rkegren
body: Great to hear about large upgrade efforts, excitng! I would do them one at a time and the database upgrade last.

Make sure you look at the minor and major version release notes for each application to see what actions to take, especially regarding user mgmt with Crowd. Then you can figure out the order.

I am not sure this is still applicable but be aware that JIRA 6.2 (or 6.1.7) not support Postgres 9.2

See: [](https://confluence.atlassian.com/display/JIRA/Supported+Platforms)<https://confluence.atlassian.com/display/JIRA/Supported+Platforms>

Still on Postgres 9.0 :-(

Cheers,

// Svante


Tags: upgrade
How to make Crowd auto start when host boots??
Asked by Peter Gilbertson:

Hi all, my company uses crowd on an on-premise machine to handle authentication between all of our atlassian products. Yesterday we lost power to the building, we quickly found tht we could not log into any of our products after the power came up. Low and behold crowd was not starting when the host machine rebooted.

Is there somewhere i can set this setting? The machine is running OS X.

Is it possible to set the init run level for the program via terminal?


Answers:
author: Tiago Comasseto
body: Hi Allen,

In this [page](https://confluence.atlassian.com/display/JIRA/Starting+JIRA+Automatically+on+Linux) you have the instructions to create a start/stop bash script (it's for JIRA, but works the same way for Crowd). This page has instructions to execute it automatically on Linux, but you can skip this part and just create the script. After that, you can set it to execute automatically on your mac as in this [online article](http://stackoverflow.com/questions/6442364/running-script-upon-login-mac).

I hope it helps.

Cheers


Tags: crowd-administration
crowd with AD connector: how detect disabled users ?
Asked by C. Faysal:

hey folks,

is there a way to detect ex-employees and deactivate automatically so that there is no manual action needed?

we connect crowd to our AD through a Active Directory Connector...unfortunately it returns all records based on the used search string...so when an employee leaves the company some bits are being set on his AD record...i could filter on that one but it will remove the entire record from the results entirely. what i need is to deactivate this employee in crowd so that the "Disabled" flag gets synced to all connected applications like Jira, Confluence etc.

is this possible?

regards


Answers:
author: Caspar Krieger
body: Support for Active Directory disabled accounts was added to Crowd 2.7 ([CWD-995](https://jira.atlassian.com/browse/CWD-995)), so if you're using that version or higher then you should see the user get disabled in Crowd when they're marked as disabled in Active Directory.

comments: author: Septa Cahyadiputra
body: Try to disable incremental synchronization feature and see if the changes picked up.


author: C. Faysal
body: im on 2.7.1 ... how does that happen? ive asked some AD guys from the company and they said that on disabled accounts a specific bit is being set.

still those users ware active in crowd. what exactly must happen on AD side in order to get them disabled in crowd ?

Thank you Caspar

C


author: C. Faysal
body: hmmm i found some setting in the directory connector

Manage User Status locally:

If ticked, you can activate and deactivate users in Crowd independent of their status in the directory server.

i see that this was ticked before...does that mean it will ignore the AD settings completely?


author: Caspar Krieger
body: Yes, if "Manage User Status Locally" was ticked, then Crowd will ignore whether the user is disabled or enabled in Active Directory. You should untick that if you want to use Active Directory to manage whether a user is enabled or disabled (note that the active/disabled status in Crowd will then be overwritten with whatever is in Active Directory on the next sync).

The background is that we introduced that option to keep backwards compatibility with existing installations of Crowd (i.e. to avoid enabling users which were intentionally disabled in Crowd but enabled in Active Directory); newly created Active Directory connectors should default to using the Active Directory server to determine whether a user is active or disabled.


author: Jackie Chen
body: Use CrowdLess - a free tool that allows to sync disabled account from Active Directory to Crowd. Here is the GitHub link: <https://github.com/jc1518/CrowdLess>


Tags: crowd-administration
Multiple crowd instances
Asked by thomasberger NA:

Is it possible to run multiple crowd instances on the same host server? I found how to [customize the port Crowd uses](https://confluence.atlassian.com/display/CROWD/Changing+the+Port+that+Crowd+uses), but no other related notes or warnings?

Thanks,

Thomas


Answers:
author: AnnWorley
body: Hi Thomas,

As long as you install each instance in it's own Tomcat container and use different ports it should be fine.

Cheers,

Ann

comments: author: thomasberger NA
body: Thanks, we are using the 'Standalone' version of Crowd which comes with Tomcat bundled so it should be alright.


Tags: crowd-administration
The password could not be changed by the credentials provider. The following URL does not specify a valid Crowd User Management REST service
Asked by Savvier Dev:

I'm trying to simply reset my password. I receive the reset password email, and land on the page without issue. Once I enter my new password and click reset, this error pops up above the password input fields.

The password could not be changed by the credentials provider. The following URL does not specify a valid Crowd User Management REST service. <http://xxxx.atlassian.net/crowd/rest/usermanagement/1/user/password?username=xxxx>


Answers:
author: Savvier Dev
body: I'm using Jira OnDemand (I believe), logging into their servers. I contacted support and they told me that they had to "re-sync the user directories". Was able to send myself a password reset after that and everything worked

comments: author: Rodrigo Girardi Adami
body: thanks for sharing the result here! i'm sure it will help many others too. :)


author: Rodrigo Girardi Adami
body: Hello Shean,

This can be problem with the Crowd URL (if you have a proxy in front possibly) or a problem with the user directory. You may want to remove and add the user directory in Crowd with the exact same configuration as this usually helps fixing many issues.

Regards,

Rodrigo

comments: author: Joonho Um
body: Hi, I also have same problem but I do not use proxy.

How can I remove my user directory?


author: Joonho Um
body: Hi, I also have same problem but I do not use proxy.

How can I re-sync my user directory?


Tags: password

reset
Backup LDAP in Crowd
Asked by Peter Van de Voorde:

Hi All,

Does anybody know if you can easily install a Backup LDAP in Crowd?

This LDAP should only be used if the Main LDAP Server is down.

Is there an easy way to copy the groups and to keep them synced if you manage your groups in crowd?

Just wondering.

Best regards,  
Peter


Answers:
author: Andrew_Sheedy
body: An approach would be to setup your second LDAP server to replicate from your primary server.

Then in crowd, specify both directories with the replicated server with a lower priority as the first.

That way, crowd will use your primary server, only looking up your second should there be a failure (authentication or otherwise).

comments: author: Peter Van de Voorde
body: Hi Andrew,

Thanks for your response, the approach you suggested is also the one I want to follow. The problem is that my groups are managed within crowd. So I would need to manually copy all the groups to the new LDAP directory.

So now I'm wondering if there is a way to copy these groups automatically within Crowd.

Best regards,

Peter


author: Andrew_Sheedy
body: Ah, sorry didn't notice that part of the question.

There's 2 approaches.

Under the User menu, you can use the Import Users section to import from one directory to another.

If your users are already migrated (and not the groups), then you can use the CSV Importer in the same section. The trouble would be to get your existing user \> group memberships, though you could figure this out using the REST api.


Tags: crowd-administration
How does the authentication work in Delegated Authentication directory?
Asked by Ravi Nair:

If I have a Delegated Authentication Directory configured in Crowd and I happen to add a user(say John Smith, username : jsmith) in this directory with password "password123". Now if this user attempts to login to an application (say Bamboo) that is using Crowd for user auth, does Crowd delegate the authentication to the Active Directory or does it try to authenticate against the internally stored 'password123'?


Answers:
author: Jobin Kuruvilla [Adaptavist]
body: It will always use the AD password since it is in a delegated authentication directory. Password doesn't make sense there but I guess they use the same "Add user" screen in case you want to manually add the users.

But you don't have to manually create users since the user will be copied over from AD when the user logs in for the first time.

comments: author: Ravi Nair
body: Great. Thanks! It seems to work as you described!


Tags: crowd-administration
What happens when we're over the user tier limit in crowd?
Asked by Paul Mokbel:

Simple question: We currently have 25 users on Jira, Confluence and Stash and upgraded the licence from 25 for each to 100 for each. We have a crowd instance with a limit of 50 users. What will happen to all of these once we go above 50 users?


Answers:
author: BernardoA
body: We suggest you to renew your license or disable some users to don't count against the license.

Cheers,

Bernardo


author: Adrien Ragot 2
body: Login is disabled and you're redirected to a page where you can change the license. If you want to remove users after reaching your limit, you'll have to enter a temporary evaluation license.

See [Crowd Licensing - Exceeding your license limit](https://confluence.atlassian.com/display/CROWD/Licensing#Licensing-WhattoDoiftheNumberofUsersExceedsyourLicenseLimit) for more details.

Regards,

Adrien


Tags: crowd-administration
Cache enabled option absent in crowd.
Asked by Tarun Sapra:

Hi the Cache enabled option is absent in the details tab of crowd directory Delegated Directory Type, microfost active dir.

Crowd version - 2.4.0

Anyone else faced this issue?


Answers:
author: Caspar Krieger
body: Delegated directories are always "cached", because in a delegated directory the "cache" is not actually a cache but is instead the "source of truth" (which can optionally be updated for a user as they log in if you enable that option). In other words, what you're seeing is Crowd working as intended.

If you're looking to regularly synchronise information from an LDAP directory to a Crowd directory, you should use a connector instead.


Tags: crowd-administration
Group mappings in crowd getting lost
Asked by Tarun Sapra:

Hi,

For all newly added users in crowd that belong to the delegated microsoft active directory, the group mappings are getting lost, has anyone faced this issue before

UPDATE - in the details tab of a groups i see this msg "Cached locally from remote directory" could this be causing the problem, if yes, any suggestions how to fix?

thanks,

Tarun


Answers:
author: Rodrigo Girardi Adami
body: Hi Tarun,

This might be related to the LDAP directory cache in crowd. These issues usually are fixed by removing the directory and adding it again with the exact same settings. I recommend to backup the application before, just to make sure.

Cheers,

Rodrigo

comments: author: Tarun Sapra
body: it was a caching issue.


author: Caspar Krieger
body: Regarding "*This might be related to the LDAP directory cache in crowd",* if it's a Delegated Authentication connector then it's not that Crowd is maintaining a cache (because in that case, Crowd has no cache and only has the authorative group mappings, but those mappings can be added from the upstream directory on user login; a subtle difference).

I would guess that this is caused by [CWD-3796](https://jira.atlassian.com/browse/CWD-3796), which makes sense if you have multiple directories mapped to the application experiencing this. If you're not sure or that doesn't apply to you, I recommend you [create a support issue](https://support.atlassian.com/) so we can help you work out what the problem is.


Tags: crowd-administration
Crowd cannot be started as your evaluation period ended *URGENT*
Asked by Marcel Montel:

Hello.

<br />

I've been setting up an upgraded test environement with crowd, jira, confluence and fisheye. Our company has licenses for the old versions, but i used the evalution on this project, to add our licenses later on. The project has been on hold for a while and now i can not start my test environment anymore because the evaluation period has ended. Is there any way to reset the eval period or for me to insert our real licenses somwhere so i can start the services?  

Regards  
M


Answers:
author: Marcel Montel
body: They do indeed, i reacted on the output from the logs which said FATAL and that it could not start, the problem was new ssl certificates on my end.


author: Nic Brough -Adaptavist-
body: The system should still run and give you a link to get to the licence screens. What are you actually getting when it starts?


Tags: crowd-administration