As an admin, how do I reset a user's password in Cloud?

Esther Strom

I'm the admin of an on-prem install that we're in the process of moving to cloud. I'm having a major issue dealing with user accounts. First, there doesn't seem to be a way for me to manually create a user account, including providing the initial password - there's only Invite Users. Even if I choose to not send an email notification, it still doesn't give me the usual form (from on-prem) that allows me to set their password.

Second, once a user is created, I can't seem to find a way as an admin to reset their password. I'm looking at the User page now, and there's a reset password  button, but all it does is send an email to the user.

This is a major problem, because we have some users that aren't actually people - they're accounts that are required for various third-party systems to connect to Jira, and the email addresses associated with them are not real. 

So how can I reset the password of a user without needing access to their email?

Daniel Eads

Hey Esther,

Any Cloud integrations you're looking to install should use the Atlassian Connect framework. On the backend this uses OAuth to handle authentication and username/passwords shouldn't be given to the external applications. If you're finding someplace where this isn't the case, please let us know!

In the case where you might have a script or something that wants to run as a particular user, you can use tokens instead of a dummy account with a shared password. Check out our documentation about using tokens. A major benefit of this is that you can issue multiple tokens per user and just revoke any tokens that may have been compromised instead of having to reset the password (which maybe was shared with multiple applications). These are specifically for the REST API and will show as run by whatever user created the tokens.

Coming from a Server-administration world, I can definitely see where you'd have multiple dummy accounts. My recommendation for trying to get these working with Cloud is:

1. Check the marketplace for any Cloud-specific integrations with your other products. These will use Atlassian Connect and avoid any app-as-a-dummy-user situations.
2. Create an email account to handle notifications from any on-prem services you have that can't use Atlassian Connect. I'd recommend this to be something like jira-integrations@yourcompany.com
3. Create a Cloud user called something like jira-bots using the email address you just set up
4. If you've verified your domain, you (and your fellow site administrators) can switch to the jira-bots user. Otherwise, you will need to set up a password for the account and log in using the password
5. From id.atlassian.com, create API tokens for each of the on-prem services you need to connect to Jira/Confluence Cloud.
6. On the "other system" side of things that formerly needed a username/password, replace the username with your Cloud bot account and the password with the application-specific API token you generated. The API tokens will transparently work like a password for anything that's connecting to the Cloud API.

There are a few small differences between the Cloud and Server APIs, so not everything that works connecting to a Jira Server instance will work by just changing the address to your Jira Cloud instance. But for the most part, this will get things rolling!

Cheers,
Daniel