Group Memberships Are Not Being Automatically Added to Users When Authenticating

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.


Crowd is configured to automatically add users to a group when they log in to a connected application.  However, if the user has had their group membership revoked, the auto-add action does not work if they log in again.

Steps to reproduce

  • In Crowd 3.1 or later, configure Crowd to grant group membership to a specific group upon authenticating in an application (like Confluence or Jira)

  • Log in to the connected application with a user

  • Back in Crowd, confirm the group was added.

  • Remove the user's membership from that group
  • Have the user re-authenticate to the connected application.
  • The group will not be re-added in Crowd


When performing the action to automatically add a user to a group, Crowd also adds an attribute to that user:

The attribute means that the automatic group addition has run for this user for the application with the ID of XXXXXXX.  You can confirm your application's ID by going to the Applications page in Crowd, and clicking on the application.  You will see the page that is loaded has a URL ending in {{viewdetails.action?ID=XXXXXXX}}.  This ID should match the ID in the user attribute previously noted.

When this user logs in to the application with the above ID, Crowd looks to see if this attribute exists and is set to true.  If so, it will skip the auto group add process.


To get the auto group add process to run again for this user, simply remove the autoGroupsAdded attribute, or set it to false.  Either way will allow the process to run for this user next time they authenticate against this application.

Last modified on Jan 15, 2019

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.