Same problem as Don. Crowd doen't seem to work with the non licensed JSD customer.

Hi I am a little confused because I use crowd and have SSO between my confluence and JIRA instances which works fine for the persons that have a confluence login. Since the intent in the 3.1 release was to allow external customers to access the knowledge base without having to count against the confluence license base ( and without making the space open for anonymous login ) i still do not see this as a fix, unless i am missing a setup somewhere or really not getting it?
Additionally is there a release that is moving the login to JSD because i read the fix but i do not see how to move the login to the service desk side?? Thanks

Hi Nik,
For the moment JSD-3751 is our proposed solution for this.
There are workarounds available - namely using Crowd as your shared user base with cookie-based SSO ( https://www.atlassian.com/software/crowd)
You may be able to use alternative SSO approaches, but these have not been tested.

Thanks,
Marty

Marty - does this mean Atlassian will not work on fixing this properly, or is the login prompt inside the modal just a temporary stopgap? While better than the redirection, it would still require users to log in twice with the same username/password for what is perceived as the same "service desk" experience.

Thanks!
Nik

Hi don.brocker,
3751 should be viewable now. Please let me know if you still cannot access it.

Thanks,
Marty

Apologies - looks like overzealous spam protection has kicked in.
Working on making it visible to you.

Marty,
When I click on the link for the jira.atlassian issue 3751 it takes me to a page that says i do not have permissions or it has been deleted. Can you make it accessible so that myself and Steven Denning-Garrison can view it. Thanks.

Hi don.brocker, nstephens, steven.denning-garrison2064237411, agoncalves,
we've spent some time analysing this and have proposed the following suggestion as the way forward: https://jira.atlassian.com/browse/JSD-3751

This will bring the login prompt into the modal dialog rather than opening in a new tab.
This is not perfect but is certainly progress on today's behaviour.

Please watch the suggestion for updates.

Thanks,
Marty

Sorry I was logged in as Don when I wrote the above. I will capture the issue if needed on a Camtasia video and attach if there is still an issue?

Marty I am with Nik on this one. The issue is not licensing nor setting Confluence to link with JIRA correctly. I myself as NIK administer both applications. My customers(for JSD) are all external. When they type on the portal they see the KB articles but when they attempt to link to them they are asked to login to Confluence. If they click on login they are able to login with there Portal login information and then see only the KB articles. I believe the intent was to allow JSD customers to be able to see KB articles without having to take a Confluence license nor open our Confluence KB space to anonymous entry, at least that is how I read the release notes and improvement requests for this. Now that my organization has released the JSD portal to a very large user base and toted the KB I would hope the functionality does make a patch soon.