Just like Atlassian does for Community, we want our customers to choose how to authenticate. They should be able to login using the Microsoft 365 work/school account, or Google ID, or Apple ID, or Slack, ...
Our customers are business people (mostly G-Suite/O365) with their own work authentication, password, and MFA policies.
We don't want to force them to create another ID.

+1 We would much prefer ** customers be able to login with Google or 365 etc v.s. agents.  Agents are employees and can do what they're told to do, getting customers the ability to sign in easily is way more important.

I just want to add to this with a walkthrough:

• Report bug to Company
• Company sends email with a "Check report status" button which links to https://_company_.atlassian.net/servicedesk/customer/portal/2/IN-...
• Redirects to https://company.atlassian.net/servicedesk/customer/portal/2/user/login?destination=portal%2F2%2FIN-...
  • "Login with your Atlassian account to view your request."
  • My existing Trello/Atlassian account is a Google login account. There is no Google login feature on this page. Typing manually will not work.
    • No alternative account/email will work, due to lack of permissions. Only the email the report was sent to has permission, which is the Google account email.
• Customer has no way to view the portal or contact the sender of the no-reply email.

I hope you understand it clearer. It needs fixed ASAP.

What is the current solution?

This is a strange oversight. We need a login with Google button.

To login to service desk I have to find a new email address somewhere because an "An account already exists" for my google account. Sometimes it will send a "An account already exists for" email, but only once when I tried. Usually it only sends the "Finish signing up" email. The whole process is broken and needs fixed.

Edit: I got around it by entering

regularemail+servicedesk@gmail.com@gmail.com and clicked the resend email button a lot, and then the "Sign Up" button many times inside the "Finish signing up" email before it eventually displayed a name/password creation screen.

But this causes another issue - https://community.atlassian.com/t5/Jira-Service-Management/Error-message-quot-You-don-t-have-permission-to-view-this-portal/qaq-p/1404099

So you can't even follow a link to a "Check report status" because they sent that email to your regularemail@gmail.com, but you're logged into regularemail+servicedesk@gmail.com, because it won't let you login to regularemail@gmail.com...

This entire process is trash. Are they not confused by the lack of activity/comments on their reports because nobody can access them?

Google Workplace or Microsoft 365 account should be able to create an account and/or login.

Thanks for your feedback Mads. 

This is something we are considering as a part of our wider customer management strategy. I will update when it has some more solid movement.

Before you did the latest authorization update on login, it worked as it should.

Now, when new employees wants to get access to our customer portal, they are required to log in through the Atlassian portal, which then create a Atlassian account (They always uses the "Login with Google" function), and then because we do not assign any groups to new users, they can only request access to Atlassian product (but NOT customer access).

When the access our customer portal link, and if they have never accessed the product before - they are met with the attached image. Here there's no "Login with Google", which makes absolutely no sence, and therefore they have to create a account, which again does they will request for access which spams our Atlassian Admins.

So my request, Please bring "Login with Google" on the customer portal (If not logged in)

@donovan marshall. and others. does this mean you invite them as "users/agents", disable their access to products, send them to the portal?

Any update on this?

Would be nice to add all social login service options for our customers (Google, Yahoo, Facebook, etc.).... the workaround for Google requires you to store the customers as a part of G Suite.  If your customers are stored in a different directory, but internal users are part of G Suite, it becomes very difficult to keep a customer directory in sync.  We would love to be able to sync our customer directory with Jira Service Desk in a better way that shares login information with our internally built services.  Currently we jump through a lot of hoops to add customers via REST API and that does not even let us update them after they are added (hopefully next version of that API will allow updates).  If anyone has any other ideas in the mean time, I would love to hear them.