Compatibility CAA - Mac Catalina - bug

 you said you couldn't copy the file over to Shared. Is there an error popping up? Have you tried copying it via Finder instead?

Sivu 

Yes, I tried manually. Same behaviour!

The same behaviour on 17.5 MR8

Regards

Looks like a regression from Apple - just like with iOS 13, will take a look at it asap. 

As Stuart mentioned, this is likely caused by changes Apple have made to the required certificate criteria when they authenticate certificates.

We are planning to update the generation of the default Appliance Certificate to meet these new criteria but were unable to get this done in time for this EAP release, unfortunately. We also expect to make this change in an upcoming MR for version 17.5.

In the meantime, to support users running Catalina or iOS13, you should look at using a certificate that is signed on a different system, which meets the criteria set out in the Apple article. You can create a CSR and the accompanying private key on the XG firewall, but the signing process, which will set the expiry date and the 'Purpose' fields, will need to be carried out on a system where you can ensure the right values are set. We'll investigate further and try to come up with some more specific instructions soon.

 as expected, there are some changes in the latest macOS that target folders and permissions. Indeed, the CAA installer can't be used anymore to copy the CA inside the /Users/Shared folder.

As a workaround, after mounting the downloaded .dmg file, use 2 Finders to drag and drop the certificate from the CAA image to /Users/Shared. Eventually, you will be asked for the user password before the operation can be executed. In any case, it will work.

Now you can authenticate the user, no popup should be seen (assuming the right XG is still the default gateway). The Trust API still works for CAA, no extra steps needed.

 as expected, there are some changes in the latest macOS that target folders and permissions. Indeed, the CAA installer can't be used anymore to copy the CA inside the /Users/Shared folder.

As a workaround, after mounting the downloaded .dmg file, use 2 Finders to drag and drop the certificate from the CAA image to /Users/Shared. Eventually, you will be asked for the user password before the operation can be executed. In any case, it will work.

Now you can authenticate the user, no popup should be seen (assuming the right XG is still the default gateway). The Trust API still works for CAA, no extra steps needed.

Sivu 

you workaround does not work. I tried already your method (certificate copied 10th of october) but same issue.

XG is the DG.

I see. Let's take it privately and work together on it, if possible. We can't reproduce this here yet.

Hey guys,

what is the status of this issue?

Since ill upgraded to catalina, ill facing this issue too.

Hoping refresh 1 has the fix.

I suspect the way to overcome the issue is generate a CA with a 2 year life to comply with the Apple new requirements.

Ian

I had the remote session with a dev and they need to fix it as something is wrong. I am not sure that will be fixed in short time. Hope to get it in GA.

Short update: the issue is not related to Catalina or certificate requirements, it is purely a (server) XG-side problem. No need to do anything about it on the Apple side.

Still investigating it, in any case this should be fixed by GA.

The issue still exists in v17.5.9 for mail. https scanning works fine.

Ian

Do you have the issue with 17.5.9 only with Catalina or also with earlier versions?

Hi Sivu,

I  only have  issues with mail scanning on Catalina, HTTPS scanning works. I am still investigating my iPhone https scanning, the iPad works with https scanning.

I have been concentrating on getting an v18 EAP box working.

Ian

Hi Ian,

I was referring exclusively to the Authentication Agent, if there are any issues authenticating against different XG versions from different macOS versions.

Sivu