P: (Early Access) Content Authenticity Initiative (CAI) for (CR & LrClassic)

It would be very useful to have a flag (or something similar) allowing the author to certify that the image was created without AI.

It would be very useful if there was the possibility to connect with the italian digital identity SPID.

I think we need more options in what is embedded. I'd like the option to simply state that no generative AI was used and there was one source image (no thumbnail for the said ingredient).

If I uncheck add watermark and change the resize to 35%, it says "Couldn't apply Content Credentials.". But if I leave it at 50% resize with watermark added, it exports the image fine.

Unabke to export photos from Camera Raw with content credentials... Consequently cannot export with Copyright

I am unable to share too many details for business infosec reasons. I'm currently using Adobe Bridge 14.1.3 on Mac OS, and I'm using this version specifically in order to avoid the forced use of "CAI." I work in image production in the entertainment industry, and there is great and growing concern that this unwanted Adobe-proprietary format is being forced on us - and that is indicated by the Creative Cloud descriptions and various submenus of the newest versions of Adobe Bridge, Lightroom, Photoshop, and Camera RAW.

This "Content Credential" product is NOT a well-accepted nor industry-adopted standard or system for data management, nor is its use recognized as a best practice by any major corporate businesses in the photography industry, especially not in the realm of entertainment photography where I've worked for 20 years.

Disallowing the ability to erase faulty, mis-entered, or even personally-identifying editing and file metadata, even when it is "junk data" or traces left by users/vendors who aren't image owners, is a complete failure point conceptually for infosec as well as for the whole idea of using Adobe's "Content Credentials" for data management. The uploading of privately-owned and proprietary images to Adobe's "Cloud" service alongside these "Content Credentials" is another separate and unique security violation. These are just a couple of many systemic failure points of this format that make it especially unsuitable for the professional image production environment. Businesses that work in imagery have a direct, easily understood business need to erase and/or change metadata. That's been true of every single photo business and photographer I've worked for and worked with.

If Adobe takes further steps to force the adoption of this protocol that breaks actual established industry best practices for data management (the ability to erase personal private identifying information, and the ability to erase and wipe old/incorrect metadata) it will drive Adobe business customers to seek other options, and to forego further Adobe upgrades and product purchases. Simply put, these Adobe "credentials" must be kept entirely optional and they must remain dormant unless affirmatively requested. And Adobe needs to be much, much clearer that that is going to remain the case.

What's the difference between this and simply adding metadata to my exports? 

There seems to be some sort of glitch where the content credentials are not always able to be added. It will work sometimes and then others it will say content credentials failed and then it wont save the file at all until I click the credentials tab off.

In the dialog description it says "seperate". "separate" would be more accurate.