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 - apache http server authentication integration problem


I would like to use crowd as authenticaiton backend server integrating with apache http server as http authenticaiton mechanishm. I've followed document below;

I'm getting this error;

[error] CrowdAuth: Failed to authenticate application.

- configuration;

<Directory "/var/www/">
  AuthName crowd
  AuthType Basic
  PerlAuthenHandler Apache::CrowdAuth
  PerlSetVar CrowdAppName XXX
  PerlSetVar CrowdAppPassword XXX
  PerlSetVar CrowdSOAPURL
  PerlSetVar CrowdCacheEnabled on
  PerlSetVar CrowdCacheLocation /tmp/CrowdAuth
  PerlSetVar CrowdCacheExpiry 300
  require valid-user

what did i check;

- application name and password correct, i also try with another application name and password it works with restfull api.

- i have checked remote ip configuration, i'm sure i added server's real external ip.

- i got tcpdump on the crowd server, it's below;

09:56:22.769876 IP xx.54627 > Flags [P.], seq 2995895305:2995896539, ack 2611274641, win 281, options [nop,nop,TS val 254446793 ecr
 3787739752], length 1234
6"..c.....      ........+......
.*....RhPOST /crowd/services/SecurityServer HTTP/1.1
TE: deflate,gzip;q=0.3
Connection: TE, close
Accept: text/xml
Accept: multipart/*
Accept: application/soap
User-Agent: SOAP::Lite/Perl/0.714
Content-Length: 933
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
<?xml version="1.0" encoding="UTF-8"?>
    <namesp1:authenticateApplication xmlns:namesp1="urn:SecurityServer">
        <credential xmlns="">
          <credential xsi:type="xsd:string">XXX</credential>
        <name xmlns="" xsi:type="xsd:string">XXX</name>
        <validationFactors xmlns="" xsi:nil="true" />

- at the crowd server, the application is active.

- crowd url is correct, when i try with with curl, it works;

[Invalid SOAP request.]

Could anyone help me to solve the problem.


1 answer

1 accepted

2 votes
Answer accepted

I see your Apache settings are a bit differente than the example in our site, have you tried with the example configuration in step 4?

<Directory "/var/mysite/">
  AuthName "Atlassian Crowd"
  AuthType Basic
  AuthBasicProvider crowd
  CrowdAppName myappname
  CrowdAppPassword mypassword
  CrowdURL http://localhost:8095/crowd/
  Require valid-user


The configuration that you referred is for the 2.x version of Crowd-Apache Connector and it doesn't support ubuntu 12.04. As document says, i've used Crowd-Apache 1.4 Connector, documanted below;

Am i wrong?

"This document is for the 2.x version of Crowd-Apache Connector, if you can't find an compatible version of the 2.x Subversion Connector for your O/S in the table below then refer to the 1.4 version of the Crowd-Apache Connector."

I'm pretty sure I've tested apache connector 2.0 with newer versions of Ubuntu, I believe our docs are outdated. I've opened this request to review this information:

In the meantime, if you have a test server, you may want to test apache connector 2.0.


Thank you Tiago. Using documentation i've easily configured 2.0.


I'm glad to hear that, if you thing this question was answered satisfactorily, you may accept the answer, this will increase its visibility and may help others in the future.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events