SCIM user and group provisioning for miniOrange IDP in Atlassian
The User Sync & Group Sync app provisions users and groups from miniOrange IDP into Atlassian using SCIM. Provisioning is event-driven: when you create, update, or deactivate an account in miniOrange IDP, the change flows to Atlassian automatically. Administrators manage accounts in one place instead of two.
This guide covers Data Center and applies to Jira, Confluence, and Bitbucket. The steps are the same in all three; where navigation differs slightly, both paths are noted.
Before you begin
You'll need:
- Atlassian Data Center, with system administrator access
- A miniOrange admin account, with permission to configure provisioning settings
- An Atlassian instance URL reachable from miniOrange IDP (public, or allowlisted for miniOrange provisioning IP ranges)
- The User Sync & Group Sync app installed and licensed (see below)
Provisioning is one-way: miniOrange IDP → Atlassian. Changes made directly in Atlassian to a synced user may be overwritten on the next sync cycle.
Download and Installation
- Log in to Atlassian as an administrator.
- Go to the administration area and select Manage Apps.
- Select Find new apps.
- Search for miniOrange User and Group Sync.
- Select Try free to start a trial, or Buy now to purchase.
- Enter your details and select Generate license on MyAtlassian.
- Select Apply license.
Step 1: Get SCIM Client Details
- Open the app and go to the Configuration tab.
- Select miniOrange as your provider.
- In the dialog, select SCIM as the synchronization method.
- Enter an App Name and select Save Settings.
- Copy the SCIM Base URL and SCIM Bearer Token. You'll paste both into miniOrange IDP in Step 2.
Treat the bearer token like a password. If it's exposed, regenerate it from this screen; the old token stops working immediately, and you'll need to update miniOrange IDP.
Step 2: Create the SCIM app in miniOrange IDP
- Open the miniOrange Admin Console and log in.
- From the sidebar, select the Apps tab.
- Click the Add Application button, search for SCIM, and select the SCIM Server (Destination) Application from the results.
- Enter an Application Name for your SCIM application.
- For Base URL and Bearer Token, use the values you copied from Step 1.
- After entering all the required information, click Test Connection to verify the integration. If the connection is successful, a confirmation popup will appear.
Step 3: Configure user sync settings
In the app, select User Sync Settings from the left sidebar.
| Setting | What it does |
|---|---|
| Directory Selection | The Atlassian directory where SCIM operations run. Users and groups from this directory are created and updated. |
| Enable Import Users | Import active miniOrange users into Atlassian. |
| Regex on Username | Transform the username received from miniOrange. Example: to convert demouser@example.com to demouser, use (.*)@.* as the regex and $1 as the replacement. |
| Enable Update Users | Update existing Atlassian user profiles when they change in miniOrange. |
| Enable Users | Activate an Atlassian user when their miniOrange account is enabled. |
| Disable Users | Deactivate an Atlassian user when their miniOrange account is disabled. |
In Jira, you can also set a Default Project Lead and Default Component Lead for newly provisioned users. Lead for newly provisioned users. These fields don't appear in Confluence or Bitbucket.
Select Save Settings.
3.1 Attribute mapping
Map miniOrange attributes to Atlassian attributes. Defaults:
| Atlassian attribute | miniOrange attribute |
|---|---|
| Username | userPrincipalName |
| Display name | Full name |
Change any row to map a different source attribute.
3.2 Custom attributes
Create custom attributes and populate them from miniOrange. Choose the source attribute, give it a display name, and it appears in the user's Atlassian profile.
Step 4: Configure group sync settings
Select Group Sync Settings from the left sidebar. Set Default groups for new users or all users, then choose a mapping mode.
On-the-fly group mapping: users are added to the Atlassian group matching their miniOrange group name. If the group doesn't exist, it's created. You can preserve existing group memberships, filter which groups sync, and apply regular expressions to group names.
Choose this when your miniOrange group names are already the names you want in Atlassian.
Manual group mapping: map each miniOrange group to a specific Atlassian group by hand. You can import miniOrange groups, filter them, and choose whether to preserve existing members.
Choose this when Atlassian group names differ from miniOrange, or when only a subset of groups should sync.
Step 5: Start provisioning and verify
- Ensure all required provisioning toggles are enabled for SCIM operations.
- Click Save to save your application configuration.
- From the sidebar, go to Policies and select App Login Policy.
-
In the Add App Authentication Policy section, fill in the
following fields:
- Configured Application Name
- Group Name (choose Default Group by default)
- Policy Name
- Login Method
- If required, enable Multi-Factor Authentication options.
- To verify a successful SCIM connection, add or remove users or groups in miniOrange and check if these changes are reflected in Atlassian.
Step 6: Review sync history
Select Sync History to see logs for every user and group operation. Filter by application to isolate a specific connection. Start here when a user didn't provision as expected.
Step 7: Connect additional IdPs
Go to Configured IDPs and select Add new App to configure additional provisioning connections against the same Atlassian instance.
Troubleshooting
| Symptom | Check |
|---|---|
| Test Connection fails in miniOrange | Base URL and token copied exactly; Atlassian reachable from miniOrange; token not regenerated since it was pasted |
| Users provision with wrong usernames | Regex on Username in Step 3; attribute mapping |
| Users don't appear after provisioning | Directory Selection points to the right directory; Enable Import Users is on; check Sync History |
| Groups created but empty | Group members assigned in miniOrange, not just the group itself |
| Deactivations don't sync | Disable Users enabled in Step 3 |
Did this page help you?
Try it for free