We are trying to implement Service Desk but we have hit a brick wall in that we cannot figure out how we can SSO our customers into Service Desk.
Our Use Case:
1. We are a SaaS web application
2. Our users are employees of businesses who have purchased our application
3. Our users already have accounts logging them into our web application
4. We want to offer service desk as our "contact support" tool
5. We do not want our customers to have to login again to service desk after they have already logged into our application (we already know who they are)
Ideal Workflow:
1. User logs into our application
2. User clicks on "Contact Support" link
3. Service Desk opens allowing them to submit a support request
We originally thought we could use SAML for this but it appears that Atlassian requires that we own the domains of the email addresses of all users signing into Service Desk. We do not own these domains since they are owned by our customers. It would not be scalable for us to work with every customer's IT department to try to get certificates for each of their domains so that we can do SAML. Thus, I'm researching alternatives.
Can Crowd be used to SSO from our application into Service Desk without us having to own the domains of the email addresses being used by our customers?
Thanks in advance!
