Application links over https

Question

Hello!

The application links from Crowd to Confluence, JIRA, Bamboo, or FishEye/Crucible are working, but none from these applications to Crowd.

Recently I tried in Confluence to delete and recreate the invalid application link. Deletion worked, it's recreation failed in some endless loop. After removin the form to input the URL the Web browser showed something like "Consumer cannot be automaticall configured because remote consumer info not found."

Since the servers are in AWS (Amazon Web Services) not all ports can be used for communication. Are there any special requirements?

The versions of the Atlassian´products are up-to-date, except Crowd which is 3.1.2.

--

Greetings

Pete

Peter Dyballa · Answer

BTW, the correct URL to access as admin via admin.do FishEye/Crucible on the remote server (at least in AWS) is simply: https://<IP address or name>/admin/login-default.do.

--

Pete

Peter Dyballa · Answer

Logging in now works as expected again.

Thank you, Rodrigo!

--

Pete

Peter Dyballa · Answer

Hello Rodrigo!

Holidays and some employee who could not get updates for our licenses in weeks kept me from working on this problem. Sorry for keeping you waiting!

The licenses for FishEye and Crucible are OK now. I simply wrote them into config.xml since a regular login is not possible (the workaround with the admin hash works and I am logged in as admin).

The documentation at https://confluence.atlassian.com/fisheye/connecting-to-crowd-813695565.html is not correct anymore, the "User Directories" are now found in "User Setting," see attached screenshot.
This also shows that some "synchronisation" had happened shortly before, which failed. There is already a hyper-link "Directory Configuration Summary" under "Additional Configuration & Troubleshooting." Choosing that reveals:

Directory ID: 2
Name: Crowd Directory
Active: true
Type: CROWD
Created date: 2016-03-24 00:00:00.0
Updated date: 2018-08-23 11:08:54.73
Allowed operations: [UPDATE_USER_ATTRIBUTE, UPDATE_GROUP_ATTRIBUTE]
Implementation class: com.atlassian.crowd.directory.RemoteCrowdDirectory
Encryption type: null
Attributes: 
 "application.name": "fisheye"
 "application.password": ********
 "com.atlassian.crowd.directory.sync.issynchronising": "false"
 "com.atlassian.crowd.directory.sync.lastdurationms": "420"
 "com.atlassian.crowd.directory.sync.laststartsynctime": "1535015334310"
 "crowd.server.url": "https://crowd.webmiles.biz"
 "crowd.sync.incremental.enabled": "true"
 "directory.cache.synchronise.interval": "3600"
 "useNestedGroups": "false"
 "user_encryption_method": "atlassian-security"

Here the application.name is simply "fisheye" which in Crowd "fisheye/crowd" was configured again. Correcting the issue in Crowd (only "fisheye") fixed the issue for Crowd. I could pass the "Authentication test."

On the side of FishEye/Crucible I get the following as result of a test:That looks already quite fine… Here is the configuration of the application link:
Next I'll try to start FishEye/Crusible with regular config.xml file and see whether I can log in.

--

Greetings

Pete