Repository navigation
verify UI has some issues #197
Description
Hi,
I noticed a issue in the verify page: previously it's working fine, but inrecent days it shows some issues: like APP used it get the signature name and the AI tools used is a [object,object]. please check below image.
the code I used is
try:
signer_info = C2paSignerInfo(
alg=b"ps256",
sign_cert=cert_chain,
private_key=private_key,
ta_url=b"http://timestamp.digicert.com"
)
signer = Signer.from_info(signer_info)
except Exception as e:
logger.error(f"Error creating signer: {e}")
raise RuntimeError(f"Error creating signer: {e}") from e
logger.info(f"signer created in {time.time()} duration {time.time() - starttime}")
# add source file as an ingredient file.
builder = Builder(manifest)
c2pa_data = builder.sign_file(signer=signer, source_path=image_path, dest_path=output_path)
the manifest I used is as below
{
"claim_generator_info": [
{
"name": "Analytical Cloud",
"version": "1.0"
}
],
"assertions": [
{
"label": "c2pa.actions",
"data": {
"actions": [
{
"action": "c2pa.created",# asset was first created
"when": "2025-05-16T12:00:00Z",
"softwareAgent": {
"name": "chatGPT",
"version": "4o",
"schema.org.SoftwareApplication.operatingSystem": "Windows 10"
},
"digitalSourceType": "http://cv.iptc.org/newscodes/digitalsourcetype/trainedAlgorithmicMedia",
}
]
}
},
{
"label": "c2pa.training-mining",
"data": {
"entries": {
"c2pa.ai_generative_training": { "use": "notAllowed" },
"c2pa.ai_inference": { "use": "notAllowed" },
"c2pa.ai_training": { "use": "notAllowed" },
"c2pa.data_mining": {
"use": "constrained",
"constraint_info" : "Contact eamail for more information."
}
}
}
}
]
}
Activity
tmathern commentedon Nov 26, 2025
@ttbuffey Please share the asset you signed (if you can), or a signed test asset that triggers the UI issue in Verify for the
AI tool usedfield.This is likely an issue with the verify UI (which is not powered by the Python SDK). But I'd need an example of a signed asset to confirm and hand over to someone who can look into this.
In the meantime, you can check if https://contentauthenticity.adobe.com/inspect has the same behavior or not. Thanks.
tmathern commentedon Nov 26, 2025
ps: For the app/device used showing the name in the certificate (I assume that's what is called "signature", in the report?), it may be correct depending on the claim versions you sign. If it's v2 (which is the SDK default now), it would show the information from the signing certificate rather than from the claim generator. This relates to the Conformance efforts.
tmathern commentedon Dec 3, 2025
(You should also switch
c2pa.training-miningto use the matching CAWG assertions instead, whose spec is here: https://cawg.io/training-and-data-mining/1.1/)scouten-adobe commentedon Jan 16, 2026
@tmathern @ttbuffey is this topic still current? If not, please close this issue.
tmathern commentedon Jan 21, 2026
I will close the issue now due to inactivity, but @ttbuffey please reopen and attached an asset so we may reproduce the issue if it occurs again. Thanks.