Automatic login to JSD customer portal

H K
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 23, 2017

Hi there,

we have developped an app and want our customers to use our service desk if they have any problems with it. Therefore we linked the Customer Portal in our app.

Now we would apreciate it, if our customers do not have to log in to the portal. They already logged in to our app. So is there a way to link these accounts or to transmit the login data from our app to Service Desk?

2 answers

1 accepted

0 votes
Answer accepted
Bruno Vincent
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 24, 2017

Hi Heike,

What you're aiming at is called Single Sign-On (SSO). This is a wide topic, but in short it's usually provided by dedicated solutions (e.g. Atlassian Crowd) or protocols (e.g. SAML).

If you use JSD Cloud, then SAML is the way to go: https://confluence.atlassian.com/cloud/saml-single-sign-on-939718272.html

If you use JSD Server, I suggest that you first take a look at Atlassian's official documentation for SSO on the Atlassian Stack: https://confluence.atlassian.com/kb/single-sign-on-integration-with-the-atlassian-stack-794495126.html

My understanding here is that you have no SSO system in your organization and that you just want SSO between your custom application and your JSD portal. Theoretically speaking, you should be able to implement this thanks to Atlassian Seraph. The point is that it's unfortunately not possible as of today because of this open issue: https://jira.atlassian.com/browse/JSDSERVER-630

Thus you will have to rely upon a non-custom SSO system. It's a bit difficult to be more specific here as I don't have enough information about your users and your organization. If your users are Active Directory domain users, then Kerberos would probably fit your needs. If your users are internet users, then SAML would be a better one. As Atlassian Crowd is generally speaking super easy to implement, I guess you should also take a closer look at it.

H K
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 24, 2017

Thank you @Bruno Vincent.

I will check out your suggestions and talk to our system admins!

Like smorhaim likes this
0 votes
Justin Warwick October 25, 2018

@H K  Mr. Vincent gave a very good and more direct answer, but I wanted to point out that the "Issue Collector"  may meet your needs. It does not have all the same features as the portal, but it is well suited to integrating into your own applications:

https://confluence.atlassian.com/adminjiraserver/using-the-issue-collector-938847338.html

I found that it takes a different path and is assumed to be no-login, even anonymous submitters. It is set up to allow easy embedding, and there are is some official documentation for pre-filling some of the fields in the form (and a few community questions out there give some very helpful details on special cases in pre-populating fields.

This question talks a little about multi-value for Components:

https://community.atlassian.com/t5/Answers-Developer-Questions/Set-fieldValues-in-JIRA-Issue-Collectors/qaq-p/464201

https://community.atlassian.com/t5/Jira-questions/Pre-set-Component-for-Issue-Collectors/qaq-p/73825

Suggest an answer

Log in or Sign up to answer