youngmon/atlassian-qna huggingface dataset:
Create a JIRA ticket whenever a bamboo build fails
Asked by Sudarshan v:

Can we create a JIRA ticket automatically whenever a build fails in bamboo.


Answers:
author: Sherry Goyal
body: [@Sudarshan v](/t5/user/viewprofilepage/user-id/4082259)

Hello! Thanks for writing to us.

If you are aware of [Automation product](https://support.atlassian.com/jira-software-cloud/docs/automate-your-jira-cloud-processes-and-workflows/), I suggest you to use ["Deployment failed" trigger](https://support.atlassian.com/jira-software-cloud/docs/automation-triggers/#deployment-failed) where you will need to connect to "bamboo" and then you can use "Create Issue" as an action.

Just FYI, there are bunch of [smart values](https://support.atlassian.com/jira-software-cloud/docs/smart-values-development/) available related to development triggers.

Hope this helps. If not, please share the rule and error details so that I can assist better.

Cheers  
Sherry(A4j)

comments: author: Sudarshan v
body: Hi [@Sherry Goyal](/t5/user/viewprofilepage/user-id/3873899) ,

I have a query, the Deployment Failed trigger you suggested above, is it mandatory that the build has to be triggered from JIRA.

Regards,  
Sudarshan V


author: Sherry Goyal
body: [@Sudarshan v](/t5/user/viewprofilepage/user-id/4082259) Just checked with the right team, sorry there is no integration with "bamboo" as there are some technical limitations to it. Sorry for the wrong suggestion before.

So with Automation, you can't achieve what you intent to. Apologies for bringing the sad news to you.

Cheers  
Sherry(A4j)


Tags: automation

jira
Bamboo server stopped due to fatal error
Asked by lian:

We installed Bamboo server 7.0.4 at our local win 10 server. It works fine for months. Today it suddenly couldn't be accessed after the windows OS reboot.

I tried to restart the "Atlassian Bamboo Bamboo" windows service, still can't fix the problem.


Answers:
author: lian
body: I checked the log file atlassian-bamboo.log and finally realized that the bootstrap failed due to the database connection issue: Login failed for user 'bamboo'. Reason: The password of the account has expired.

It went back to normal after I fixed the database.

comments: author: Jimmy Seddon
body: [@lian](/t5/user/viewprofilepage/user-id/3093589) could you provide some more details for the accepted answer regarding how you were able to resolve this issue in case other users make their way here looking to resolve a similar issue in their own environment.
How to purge old user sessions in Crowd?
Asked by Thomas Berger:

I've noticed that in 'User Sessions' all users have multiple entries, some are several month old.

Does this mean the session never expired?

How can I purge all old sessions?


Answers:
author: Thomas Berger
body: The problem was caused by using one Crowd Application with two actual applications (shared). So creating one application in Crowd per actual application resolved the issue.
Null Pointer Error when backing up Crowd
Asked by john scancella:

When I try to backup crowd to an xml file I get a null pointer error.

com.atlassian.crowd.migration.userMapper.addUserToXml (userMapper.java:87)

I have check the database and there doesn't seem to be any null users, so why am I getting a null pointer error?


Answers:
author: JustinK
body: The line in error is most likely:

```
userElement.addElement(USER_XML_CREDENTIAL).addText(user.getCredential().getCredential());
```

Meaning that a user has a null credential, yes the code could be better, and it is a lot better in later releases of Crowd. So I would check to see if a user has a credential that is null.

comments: author: john scancella
body: Justin,

There area bunch that are null. I have crowd set up to use LDAP as the authentication method. What should the credential be(I would guess "nopass" since that is what some of the others say)?

Would it be wrong to modify the null credentials in the database? Thanks for all the help


author: john scancella
body: Sorry, I am running version 2.1.1It is currently being run on a intranet only computer. To get the entire stack trace I would have to type it all out manually, is there a specific part you want to look at that I could get? Thanks!

comments: author: JustinK
body: I am assuming that you are using a delegated LDAP directory, so all auth will happen against LDAP and not against the local database.

Putting no 'nopass' into the credential column would be fine, since it will never be used for auth and that column expects an encrypted value, so nothing will every evaluate to 'nopass'.

You have actually hit <https://jira.atlassian.com/browse/CWD-2284> which was fixed in 2.2.1 of Crowd.

As with any database change, I would recommend taking a backup of the database **before** doing this change.

Cheers,

Justin


author: JustinK
body: To help us verify the error could you let us know the version of Crowd you are using.

It would also help to have the complete stacktrace.

Cheers,

Justin


Tags: backup

null-pointer-exception
Can I use the pear php module to communicate with my OnDemand JIRA's Crowd instance?
Asked by Surajit Nundy:

Hi,

I need to have the the users of our php-based CMS (Drupal) have a single sign-on with our OnDemand instance. Is there some way in which I can use the RESTful webservice based <http://pear.php.net/package/Services_Atlassian_Crowd> to do that? It works for the standalone version.

Thanks


Answers:
author: TimT
body: Crowd is used in OnDemand only to coordinate the Atlassian applications enabled for your OnDemand account. There is currently no way to connect external applications to it.

We are interested in getting feedback from people who would like to connect external applications to your OnDemand Crowd server. There is an open feature request at [https://studio.atlassian.com/browse/JST-3397](https://studio.atlassian.com/browse/JST-3397.). Please add your vote and comment if you wish on how you'd like to use OnDemand Crowd with external applications. If we see a lot of interest in this, we'll take that into account for future development planning.

For more information on how we plan new features, please see https://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy


Tags: cloud

integration
Import salesforce.com account and contact object into crowd
Asked by ION Information Systems:

Hi,

we are evaluating the implementation of crowd as a centralized user management. a requirement for this would be to connect [salesforce.com](http://salesforce.com) to pull into crowd accounts and the related contacts. we will need then these accounts/contacts to be used as groups/users in a jira instance we use for customer support. is that possible?

thanks,

Andrea


Answers:
author: Bruna Griebeler
body: Hi Andrea and Manoj,

We have a Feature Request for it: [](https://jira.atlassian.com/browse/CWD-921)<https://jira.atlassian.com/browse/CWD-921>

We ask customers to vote on it and prove the real demand for such integration.

For now there are plugins for Jira and Confluence: [](https://marketplace.atlassian.com/search?q=sales+force)<https://marketplace.atlassian.com/search?q=sales+force>


author: DevDigital
body: Hey,

I want to achieve same things? Any idea how to do it and if its possible to implement?

Thank You

Manoj
Crowd SSO works on logout but not login
Asked by john scancella:

Here is the problem I am having. I installed and configured crowd's SSO with JIRA, confluence, fisheye, and crucible. Whenever I log into one application it doesn't auto log me into other ones. However, if I log into crowd, and into another application, and then log out of the other application, it also logs me out of crowd.

Does anyone know why this might be happening?

Here are the versions of the software I have installed

confluence 4.1  
crowd 2.1  
crucible/fisheye 2.7  
jira 4.4


Answers:
author: Jobin Kuruvilla [Adaptavist]
body: This happens when there is some issue with the setup and there is no single reason for this. For example, mistakes in crowd.properties or wrong domain can cause this!

<http://confluence.atlassian.com/display/CROWD/Troubleshooting+SSO+with+Crowd> might be a good place to start.

comments: author: john scancella
body: I can log into all the applications using crowd, but still the SSO doesn't work (unless I am logging out from an application, in which case I am also logged out of crowd.)

I can't get the log files as the applications are on a closed network and files are not allowed off of it. Is there something specific I can look for in the log files and report back with?


Tags: sso
Will crowd 2.4 work with postgresql 9.1?
Asked by Jim d:

On the Crowd 2.4 Supported Platforms page, I see that it only lists support for PostgreSQL "8.x". Does anybody have experience using crowd with PostgreSQL v9.1?


Answers:
author: Bruna Griebeler
body: Crowd 2.4 do not support postgreSQL 9.x. However it doesn't mean that it will not work. I just means that this version of Postgres is not supported yet by Atlassian on this specific version.

Cheers!


Tags: postgres
Can Crowd be used as an LDAP wrapper? and CAS/LDAP server?
Asked by Brian Mills:

I have a couple of applications including JIRA, GreenHopper, Fisheye and Crucible, as well as a source control server system.

I believe I can use CROWD to wrap 2-3 LDAP AD domains pulling some (but not all) users from each domain for authentication for the atlassian applications.

2 questions:

- Can the users who can access each product be controlled in CROWD?

- Can CROWD also provide LDAP or CAS server to the other non atlassian applications so that I have one app providing users to all my SDLC tools? (the user base is essentially the same and it would be nice to control access in one location)


Answers:
author: Colin Goudie
body: Crowd does authentication, not so much authorisation. By that I mean, you can control which applications are allowed to use crowd, in order to authenticate users, but that is just the first step. Basically Crowd is telling the application that, yes, this user is authenticated.

But then it is up to each individual application to control their own authorisation aspects based on groups/users etc.. to their respective permissions.

Crowd can be used by non Atlassian apps if the applications are able to be 'crowdified'. There are various third party extensions available. e.g. Alfresco to Crowd, Hudson to Crowd etc.. Also, any spring security web stack can have crowd functionality fairly easily added.
Sharing Tomcat binaries between Crowd & JIRA
Asked by meena radhakrishnan:

I would like to share the Tomcat binaries between JIRA and Crowd by setting up CATALINA_BASE for each. Is there any documentation on this?

thanks


Answers:
author: parthiban subramaniam
body: Have a look at

[Setting up multiple instances of tomcat](http://www.shaunabram.com/multiple-tomcat-instances/)

cheers


Tags: server

tomcat
Crowd-LDAP Integration
Asked by roopa shinde:

Hi,

I get this error when I integrate Crowd with our organization LDAP server

No results were found from your search. org.springframework.ldap.UncategorizedLdapException: Uncategorized exception occured during LDAP processing; nested exception is javax.naming.NamingException: \[LDAP: error code 1 - 000004DC: LdapErr: DSID-0C0906E8, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, v1db1\]; remaining name 'dc=xyz,dc=co,dc=in'

can anyone give me some idea on this error


Answers:
author: Aivo Kuhlberg
body: I had the same problem and simplified User DN solution did not work until I figured out my stupid mistake that together with changing the Username field I had to type the password. Then it worked.

comments: author: Vin?cius Ferr?o
body: This wasn't your stupidity. The interface is just bad and does not alert about this. Same issue here.


author: Application Services
body: I had the same error. Couldn't figure out what was wrong. Reset the password for the directory (thank you for the hint about the password), and this fixed the problem! Maybe I had a space at the end when I did copy and paste the first time.  
The error message could have been more meaningful!


author: Sadiq Hameed
body: Hi

It seems your current user has no-rights on fatching the AD details, so you have to use a user credentials that can access the AD details, like;

DirectoryEntry entry = new DirectoryEntry("LDAP://staff", "UserName", "PWD");

regards

Sadiq


author: Septa Cahyadiputra
body: Hi there,

Seems like this KB might helps you in this issue

* <http://confluence.atlassian.com/pages/viewpage.action?pageId=197298522>

Hope it helps.

Cheers,  
Septa Cahyadiputra

comments: author: roopa shinde
body: Hi Septa,

Thank you for your answer , I tried with simplified User DN, but no luck.


author: Septa Cahyadiputra
body: Hi there,

It seems that it might be due to the configuration. Could you please double check if the configured baseDN is valid. It would be great to continue investigating this issue trough [support channel](https://support.atlassian.com) since revealing your configuration in public may not be a good idea :).

Anyway, for now you might want to double check all the configuration as LDAP: error code 1 basically means that the application is not able to bind your LDAP server which might be cause by several reason such as

* LDAP/AD server name is incorrect
* Port number is incorrect
* Incorrect DN and baseDN

Hope it helps.

Cheers,

Septa Cahyadiputra


Tags: integration

ldap
Crowd switch to SQL server db
Asked by meena radhakrishnan:

Once installed with embedded DB how do I switch Crowd to use SQL Server?

Currently there is no user or directory setup yet.


Answers:
author: Septa Cahyadiputra
body: Hi there,

I think the best method for a new instance is to use the XML backup. Please try the following steps

1. [Create the XML backup of your current Crowd instance](http://confluence.atlassian.com/display/CROWD/Backing+Up+and+Restoring+Data)
2. Install a new Crowd with the new database
3. [Restore your XML backup](http://confluence.atlassian.com/display/CROWD/Backing+Up+and+Restoring+Data)

Hope it helps.

Cheers,

Septa Cahyadiputra

comments: author: meena radhakrishnan
body: Thanks Septa. I ended up reinstalling the whole setup after wiping out the CROWD HOME DIRECTORY.


Tags: ms-sql
Crowd SSO with 2 instances of Jira -- one behind firewall, one not.
Asked by Bryan Karsh:

Hi,

Here is what I am trying to do -- I want to run Crowd and one version of Jira behind a firewall, and have a 2nd external version of Jira. Basically the "internal" version of Jira would be for internal customers, and the external version of jira would be for external customers.

I've been able to get SSO to work with crowd internally --- but I am not sure how to approach it when one instance is internal, and the external.

Is this even possible?

If not, what if both Jira instances are behind the firewall, but we have proxies set-up in the DMZ -- could we get then get SSO to work?

Any tips/advice appreciated.


Answers:
author: JustinK
body: Are all users within the same directory in Crowd? Since directory id is used as a validation factor when creating the crowd token (the crowd token is used for SSO).

If this is the case, this should be a no-brainer and pretty straight forward. The other issue is that they need to be on the same parent domain, since Crowd uses cookies to provide SSO.

[external-jira.mycompany.com](http://external-jira.mycompany.com)

[internal-jira.mycompany.com](http://internal-jira.mycompany.com)

So there would be a cookie created with the domain of \*.mycompany.com

These are probably the two biggest issues that you would need to validate.
Broken Crowd
Asked by CCCP Admins:

I have a server on which Crowd runs. However, since the 15th of april, Crowd stoped working. Hist last words in his errorlog where
> 2012-04-15 22:35:10,225 Thread-21 INFO \[ContainerBase.\[Catalina\].\[localhost\].\[/crowd\]\] org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: destroy called  
> 2012-04-15 22:35:11,441 Thread-21 INFO \[ContainerBase.\[Catalina\].\[localhost\].\[/crowd\]\] Closing Spring root WebApplicationContext  
> 2012-04-15 22:35:11,475 Thread-21 INFO \[util.persistence.hibernate.ConfigurableLocalSessionFactoryBean\] Closing Hibernate SessionFactory  
> 2012-04-15 22:35:11,606 Thread-21 WARN \[net.sf.ehcache.CacheManager\] CacheManager already shutdown  
2012-04-15 22:35:11,607 Thread-21 INFO \[com.atlassian.crowd.startup\] Stopping Crowd  
And since that moment, it is impossible to start or restart Crowd in any possible way I can think of. The five lines of the errorlog above are therefore the last lines of this log. This are also the only messages in the log of that day.  
Does anybody know how make Crowd running once again?


Answers:
author: CCCP Admins
body: Problem is solved by updating Crowd. I expect a file became corrupted for unknown reasons, which would explain why updating it from version 2.2.4 tot 2.4.0 worked.


author: Colin Goudie
body: Can you backup all logs, remove them and then try boot crowd again? What does the logs say? Including possible take a look at the tomcat catalina logs


author: CCCP Admins
body: Unfortunatly, this is everything the log says about the day Crowd stoped working (15th of april). The last errorlog before this date is a list of the 10th of april, but in this list there are no unusual loglines to be found.


author: Colin Goudie
body: Any more detail you can provide from the logs? Like exception traces? That would help
LDAP authentication configuration error in CROWD
Asked by meena radhakrishnan:

The LDAP's directory configuration tab throws the following error when tried 'Test Search'.

"***No results were found from your search. org.springframework.ldap.UncategorizedLdapException: Uncategorized exception occured during LDAP processing; nested exception is javax.naming.NamingException: \[LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece?\]; .......*** '

I am creating a delegated authentication directory. When I test the connection on the 'Connector' page I am getting the following message

"The server address and port are valid. Please verify your DN settings through the Configuration panel by performing a group, role, or user search." but on the 'Configuration' tab getting the above error.

According to the doc <http://confluence.atlassian.com/display/CROWD/Configuring+a+Delegated+Authentication+Directory#ConfiguringaDelegatedAuthenticationDirectory-next>

"**Delegated Authentication directories do not allow you to browse the LDAP data** . The directory delegates user authentication to LDAP, but to be able to list users and groups, you will need to add them to the directory. See more details in the [Next Steps](http://confluence.atlassian.com/display/CROWD/Configuring+a+Delegated+Authentication+Directory#ConfiguringaDelegatedAuthenticationDirectory-next) section of this page."

The error I am getting is that due to delegated authentication directories not allowing to browse data?

Thanks


Answers:
author: meena radhakrishnan
body: I got it working now. It was due to "When creating the LDAP Connector, the administrator clicked the Test Connection Button before saving the Connector."

I am able to test the search successfully though I am not able to lookup an user in this directory. Is this a limitation on the 'Delegated Directory' part?


Tags: ldap
How do I set up SSO with crowd and two jira instances on the same box?
Asked by Bryan Karsh:

Hi,

I am setting up crowd and two instances of Jira on the same domain: [foo2.foo.net](http://foo2.foo.net)

Crowd is using port 8095 : <http://jc-prod-tomcat-102.foo2.foo.net:8095/crowd>

Jira 1 is using port 8080 : <http://jc-prod-tomcat-102.foo2.foo.net:8080>

Jira 2 is using port 8081 : <http://jc-prod-tomcat-102.foo2.foo.net:8081>

I can have Crowd handle centralized authentication no problem. But when I try to turn on SSO with the [foo2.foo.net](http://foo2.foo.net) domain, I initially get success -- I can log into one jira -- and then the other jira without logging in again. But if I log out, I am locked out of all both jiras and also crowd. I understand from reading that this is likely due to incorrect domain settings. I've tried both '.foo2.foo.net' and 'foo.foo.net.'.

Any tips?

I am using Jira 5 and Crowd 2.4


Answers:
author: Adam Laskowski
body: SSO for Crowd works via cookies for each application server. If you have more than one application running under the same context (in your case, the root context), the cookies will overwrite one another in the root context "/" and you will run into auth problems like this.  

If you run your JIRA servers on separate contexts, it should clear up your issue. Example:

**JIRA 1:**http://jc-prod-tomcat-102.foo2.foo.net:8080/jira

**JIRA 2:**http://jc-prod-tomcat-102.foo2.foo.net:8081/jira2


author: Colin Goudie
body: What are the url's of the applications? are they like foo2.foo.net/jira or [jira.foo2.foo.net](http://jira.foo2.foo.net) e.g.
Crowd Can't Send Email
Asked by Coop IT Coordinators:

After configuring an SMTP server in Crowd's Mail Configuration page, no emails are sent. The SMTP login credentials have been tested and are known to work.

There is no evidence (that I can find) of attempts to send emails, or the resultant failure message.


Answers:
author: Coop IT Coordinators
body: There was never any evidence in the logs of a failed attempt in our case. Eventually an Atlassian rep modified our database to fix the issue.

Sorry I can't help your problem!

Mart?n

comments: author: Matthew J. Horn
body: Any chance you have a ticket number or some kind of ID for a support request (we have a support contract and would love to be able to at least have some idea where to start).


author: Matthew J. Horn
body: Fair enough. We are actually having an additional problem where some log file entries are written and some are not, depending on the user directory, so I thought that might lead us down a similar path. We'll file a ticket. THanks!

matt


author: Coop IT Coordinators
body: Given that the symptoms aren't the same, I wouldn't assume that they're related. It might actually delay resolution by a support rep by confusing the sitution.

Also, I don't want to give out potentially sensitive information about our authentication system.

I would suggest opening a ticket, giving them logs, and letting them figure it out.


author: Matthew J. Horn
body: Posting here for the benefit of others.

The issue (and I am summarizing my IT guy's explanation, but what the hell) was that we whitelisted the Crowd server so that Exchange would allow emails to be sent through it. However, Exchange really wanted *credentials* from the Crowd server rather than being whitelisted. After *removing* Crowd from the whitelist, Crowd started sending the credentials (or Exchange started accepting the credentials), and the result is working emails.

Still having issues with users in one directory NOT working, but we're following up with Atlassian support on that.


author: Matthew J. Horn
body: Did you resolve this? We get a similar issue. The crowd log files show an error like this:

java.lang.RuntimeException: Could not send email to [it@mydomain.com](mailto:it@verivo.com). Reason:**No authentication mechansims supported by both server and client**


Tags: smtp