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