[Crowd] How to disable user login without deactivation?

Sameera Shaakunthala [inactive]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 19, 2014

There are situations when we need to have user accounts in JIRA/ Confluence used only for mass mailing. We create a user account with a generic username and a mailing list address, for example user is 'my-list' and email is 'my-list@example.com', and then subscribe to the updates/ filters using that account. Or else, add that account as a watcher.

For security reasons, this user must not be able to log in and also must not be able to reset the password through Crowd. Disabling the account won't work because user won't receive e-mail when disabled.

Is there any user attribute that Crowd administrators can manually set so that user won't be able to log in?

1 answer

1 vote
Caspar Krieger
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 19, 2014

I believe there's no easy way to do this (source: I'm a Crowd developer).

The closest you could do is to set the password to some unknown value in Crowd, and set up some alert to watch for the password reset email coming through the mailing list. Or filter the password reset message from being allowed to get onto the mailing list by passing it through some interceptor account first.

Or write a script to reset the password of the user every 15 seconds.. but that still leaves you open to attack by any determined attacker.

You could try removing the jira-users group from that particular user account, but I suspect that the user won't receive notification emails from JIRA if you do that.

(As a more hardcore solution, you could modify the reset password action in Crowd to protect against resetting that hardcoded user's password and then rebuild and reinstall it from source, but source modifications like that are unsupported so you may not want to go down that route.)

Zul NS _Atlassian_
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 19, 2014

Removing jira-users group membership from a user would allow the user to receive notification mails but will not be able to login to JIRA.

Caspar Krieger
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 19, 2014

So that's probably the way to go then :)

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 19, 2014

You'd also need to ensure that the user can SEE the Jira issues for which they need to be notified, which usually means they need to be in the role of "users" and the usual way to do that is to put the "jira users" group in there.

The obvious workarounds would be to enable anonymous browse in the projects (although that would let non-logged-in users see the issues), or include them some other way that does not involve using jira-users. I'd be tempted to create a role like "snoop" or "user mail", and grant that "browse" in the permission schemes. Or put all these not-really-users into a big group and put that in the schemes.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events