nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Untrusted domains - JSM users

vthomas9

HI-

JCMA is requiring that I resolve all Untrusted Domains before doing a migration.

I have 3000+ Jira Service Management users that are in untrusted domains. I do not plan to migrate these users to the cloud and I do not plan to migrate the projects they are referenced to the cloud. I have only one domain that is trusted out of the 587.

Screenshot 2023-10-03 at 1.44.36 PM.png

What is the most efficient way to deal with this issue? I am blocked in doing a migration due to this issue.

Virginia T

University of Washington

Comments

Kian Stack Mumo Systems

@vthomas9,

Have you tried the option "Migrate only the users and groups referenced in projects"?

Is it still returning all of those users with the domains?

Thanks,

Kian

vthomas9

@Kian Stack Mumo Systems

Yes, I chose that option. I selected one project to migrate, and the project only has two users in it.

Sam Nadarajan

I recently did a migration that had 3000 domains, I simply reached out to Atlassian support and they took care of it.

Hope this helps!

Darryl Lee

It's probably better to do ask for support's help, because the alternative is scripting it, which admittedly is a little hacky:

https://community.atlassian.com/t5/Atlassian-Migration-Program/A-new-security-feature-for-Cloud-Migration-Assistants-helps-you/ba-p/2192571#M968

Although in retrospect you should be able to substitute the acli command with a simple curl with a personal access token in the header, like so:

for x in `cat domainlist.txt`
do
curl --header "Content-Type: application/json" --header "Authorization: Bearer <YOURTOKEN>" -X PUT 'https://YOURJIRASERVER/rest/migration/latest/email-domain/rules' -d "{\"domainName\":\"$x\",\"rule\":\"NOT_TRUSTED\"}"
done

Note: YOU ABSOLUTELY SHOULD TEST THIS FIRST.

I just gave it a spin with about 100 domains with JCMA v1.10.0, and it seemed to work.

Note that the URL of the REST endpoint changed from when I wrote my previous script, so you'd definitely want to check with some standalone curl commands to test this before running it in bulk.

Marcin Kempa

Hi @vthomas9

Thank you for sharing this experience with the community. I am from the migration team and would like to understand the setup so that we can help you and others in similar situations.

I am sorry this is disrupting your migration process. Please open a ticket with Atlassian support so we can exchange detailed information about your setup. Please tag me on the ticket so that I can find and check it faster.

Regarding problems when validating domains, could you try to use CSV export and import in the domain verification step and mark domains you trust faster than through the UI?

Best Regards,

Marcin Kempa

vthomas9

@Marcin Kempa

Yes, tried the CSV export and import. I marked all the domains as Not Trusted except for the one domain.

JCMA requires that all domains are Trusted. It blocks the migration process at this step.

I'll open a ticket. I need a solution to this issue as soon as possible (today!) since I have a deadline to do this work by the end of the week.

Best,
Virginia

vthomas9

@Sam Nadarajan Thanks. I'll contact support.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

migration