OAuth2.0 for Customer Portal logins

[Michael Marriott]

Given that Portal Customers have an account automatically created when they raise an issue and that they need to create a password and login to that account to continue the 'discussion' and that there is no configuration around this;

It is not a good look for our organisation to have one login to our applications and then force users of our applications to create a separate account to receive support on those applications .

How can I get around this and make application use and support seamless?
Is using OAuth2.0 an option so that our Organization can be the authentication server in this model?

Mike

[Rick Westbrock]

We have the same use case where we already use Okta to provision accounts for users who need a Jira or Confluence cloud account. What we have done as a proof of concept exercise in our sandbox instance is to configure Okta to also push portal customers to Atlassian and since they do not have product access they aren't billable in Atlassian Access.

My colleague configured this and has tested it as a power user/admin but to be fair we haven't yet had any true portal customers test out the UX yet.