There's a scenario where default Crowd group memberships will not sync over to Confluence/JIRA during initial login. If Confluence/JIRA has synced with Crowd prior to the user logging in to Confluence/JIRA, the user will be placed into the correct groups in Crowd but not in Confluence/JIRA.

Steps to reproduce

1. Inside Crowd: create an internal Crowd directory. In the 'Options' tab, set it to add users to some default groups upon initial authentication
2. Inside Crowd: create a user in the internal directory but do not place him in groups
3. Inside Confluence or JIRA: create a Crowd Server directory, and trigger a synchronization from Crowd
4. Inside Confluence or JIRA: log in using the Crowd user

Expected result

• User is added to default groups in Crowd
• User is added to the same default groups in Confluence

Actual result

• User is added to default groups in Crowd
• User is NOT added to any groups in Confluence

This is alleviated during the next FULL sync from Confluence/JIRA, whether automatic or triggered manually. However, incremental syncs will NOT sync the membership info over, thus creating a discrepancy between Crowd and Confluence/JIRA.

Workaround

• Restart Confluence/JIRA. This will trigger a full sync from Crowd on application startup
• Or, if the Crowd Server user directory is set to use full sync (the incremental sync option is unchecked), you can trigger a sync manually to get the memberships over