Is .localhost a valid domain scheme for SSO?

[Andrew Pennebaker]

I'm trying to evaluate SSO by setting up a few Atlassian apps in a spare machine and configuring them for SSO. So far, everything seems to work. But suddenly, setting JIRA to use the SSO authenticator in seraph-config.xml results in the JIRA web server failing to respond to any request.

Trace:

$ tail -f logs/jira050213111531-stderr.2013-02-06.log
 at com.atlassian.crowd.integration.rest.service.RestCrowdClient.<init>(R
estCrowdClient.java:78)
 at com.atlassian.crowd.integration.rest.service.factory.RestCrowdClientF
actory.newInstance(RestCrowdClientFactory.java:26)
 at com.atlassian.crowd.integration.rest.service.factory.RestCrowdHttpAut
henticationFactory.createInstance(RestCrowdHttpAuthenticationFactory.java:43)
 at com.atlassian.crowd.integration.rest.service.factory.RestCrowdHttpAut
henticationFactory.<clinit>(RestCrowdHttpAuthenticationFactory.java:21)
 ... 40 more
Caused by: org.apache.commons.httpclient.URIException: URI-Reference required
 at org.apache.commons.httpclient.URI.parseUriReference(URI.java:1874)
 at org.apache.commons.httpclient.URI.<init>(URI.java:165)
 at com.atlassian.crowd.integration.rest.service.RestExecutor.<init>(Rest
Executor.java:59)
 ... 44 more

I'm wondering if JIRA or other Atlassian apps have trouble using .localhost as an SSO domain scheme, or if the problem is caused by something else.

[AndrewA]

Hello,
I am not sure if this is a problem with Jira or Tomcat. Either way, I take it we are trying to make distinct domains to test SSO yes? If so, a way that I know of which works is by defining a context path for each application in their server.xml file. For example, we could list our apps as follows.

HTTP://localhost:8080/Jira

HTTP://localhost:8090/Confluence

Which would make each domain unique for creating Crowd SSO keys.

Cheers,
Andrew