User athentication problems after moving from on-premises to Cloud

[Girts Palejs]

Hi all!

Maybe someone has been through this before.

I had a small Jira setup on my servers, and now moved everyhing to the Cloud - so there is more space to grow later ... 

Problem is - our partners were syncing their JAMA system to ours, and now since I moved to the cloud - they can not connect to Jira anymore.

In the old (on-prem) version each used had a Username and password  .. and JAMA connector used that to authenticate and connect to JIRA

Now - in the JIRA Cloud - there seems to be no Username  ...  just Full Name, e-mail and User ID for each user, and none of them seem to work as means of authentication when connecting to the Jira Cloud servers.

Tasktop from JAMA: Connection settings are not valid. A connection to https://xxxxxxxxxx.atlassian.net/ could not be established: Authentication credentials were not accepted by the server: Please verify authentication method and credentials are valid for the location.

Are the Usernames hidden somehwere?   I tried user export - nothing new there - same user IDs and User Names etc.

Any ideas appreciated .. 

Regards,

Girts Palejs

[Trudy Claspill]

Hello @Girts Palejs 

Welcome to the community.

When you move to Jira Cloud the old user names become meaningless. Access to Jira Cloud is based on the email associated with an Atlassian account.

What method/tool was being used to allow JAMA to integrate with your Jira system when it was self hosted? Was JAMA Connect being used, or some other method?

What authentication method was being used when you were self-hosted? What authentication method are you using now that you have migrated to Cloud? 

What authentication method was used by the Jama/Jira integration when you were self-hosted?