Assertion
assertedBy
result
TestResult
description
rsa public key has two relations for modulus
outcome
subject
x509·X509Certificate
IssuerDistinguishedName
O=FOAF+SSL, OU=The Community of Self Signers, CN=Not a Certification Authority
base64der
MIIDgzCCAuygAwIBAgIQZ84ABvhjj7hqFoWqSsvBFjANBgkqhkiG9w0BAQUFADBj MREwDwYDVQQKDAhGT0FGK1NTTDEmMCQGA1UECwwdVGhlIENvbW11bml0eSBvZiBT ZWxmIFNpZ25lcnMxJjAkBgNVBAMMHU5vdCBhIENlcnRpZmljYXRpb24gQXV0aG9y aXR5MB4XDTExMDMyODE0MDY1MFoXDTEyMDMxODE2MDY1MFowgYsxETAPBgNVBAoM CEZPQUYrU1NMMSYwJAYDVQQLDB1UaGUgQ29tbXVuaXR5IE9mIFNlbGYgU2lnbmVy czE3MDUGCgmSJomT8ixkAQEMJ2h0dHA6Ly9iYmxmaXNoLm5ldC9wZW9wbGUvaGVu cnkvY2FyZCNtZTEVMBMGA1UEAwwMYmJsZmlzaCBjYXJkMIIBIjANBgkqhkiG9w0B AQEFAAOCAQ8AMIIBCgKCAQEA5+kuueCGksuOuQciIrf7hjSRiahB8c3hd8hPjTH/ 6k+NBKN+H0MRHPiSVCVwvvhstF2zmE6Ms0NwzSDWHuSOqjEwu6+CKE8tvL0Y0OHk bkhVDhenLPQagKIWjXe0k4CDIcizyNj1L8zRwsN0TaxrYZZPlaTx2/VpMI3ApaVK yb/4+mJ4UZDBol9TMkTfyBbPq3iISMz6rt3vsNgksXar0DCftGag2V2E1L/t8Hvu De0UaqKajsIlVtu/iUMSYKu41dZJCVCYm/DrqcX0m1aUwHAYWKtSap9Z5p7PnJVo wqp2/3jnsf7h6WlUN9yQtm/FeEeMp+3Mx7DokAYYTElTaQIDAQABo4GKMIGHMAwG A1UdEwEB/wQCMAAwDgYDVR0PAQH/BAQDAgLsMBEGCWCGSAGG+EIBAQQEAwIFoDAd BgNVHQ4EFgQUzoQy71OnKyW8qE7boOHpLrjN2aQwNQYDVR0RAQH/BCswKYYnaHR0 cDovL2JibGZpc2gubmV0L3Blb3BsZS9oZW5yeS9jYXJkI21lMA0GCSqGSIb3DQEB BQUAA4GBAH0kxSBDYGAMah4cloznjsnglGNMCTd2zPtxnWDFUjuD2YWhc8QXd/k7 T1GlVZdLfT175/D7jYpXEVH7UyO8DTnttlAePmDqbspT+vcpV1orUrWlMTJ7hAzP Ev9aBOHrZPyKDeUJO0JgwAWxOU/ND347Ssg3lTbFt0jrZxDLHLxC
subjectAlternativeName
and
webProfile·Response
body
#the rdf file used. could be n3, or something. This could also point to the content?...
headers
httpVersion
1.1
test
Assertion
result
subject
and
test
Assertion
assertedBy
result
TestResult
description
webid http://user.example/#me does not have a matching public key in profile
outcome
subject
and
test
Assertion
result
subject
and
test
Assertion
result
subject
and
test
Assertion
result
subject
and
test
r05·Software
developer
name
WebID Test suite in Clerezza
programming-language
Scala
repository
test·Ontology
certificateCriticalExtensionsOk·TestRequirement
description
Critical Extensions are not a direct problem for WebID, but can cause many servers to reject the certificate before the WebID code gets to see the certificate. These tests should not generate errors but only warnings
title
The certificate contains no unecessary critical extension
certificateDateOk·TestRequirement
title
The current timestamp is between begin and end date of the certificate
certificateProvided·TestRequirement
title
The client provided a x509 certificate
certificateProvidedSAN·TestRequirement
title
The client certificate contains a subject alternative name
certificatePubkeyRecognised·TestRequirement
description
The public key in the certificate is recognised by the WebId code. If it is not then it is not going to be possible to match it with the remote certificate.
title
Public key in certificate recognised
profileGet·TestRequirement
title
WebId Profile is accessible and downloadable
profileWellFormed·TestRequirement
description
The WebId Profile is parseable Content and transformable to RDF
title
WebId Profile is well formed
profileWellFormedKey·TestRequirement
description
All the keys in the profile are well formed and not misleading
note
One does not need to test all keys in a profile, only those that are tied to the WebIDs found in the X509 cert. But to help users one could give them a deeper test of the profile.
title
WebIdProfile Contains well formed Keys
profileWellFormedPubkey·TestRequirement
description
A particular Public key is well formed
title
Public Key is well formed
pubkeyRSAExponent·TestRequirement
title
rsa:public_exponent is well formed
pubkeyRSAExponentFunctional·TestCase
description
More than one exponent if they don't convert to the same number is very likely to create erratic behavior (one server will choose one the other server will chose the other)
title
not more than one public exponent per RSA public key - or else they have to be identical
pubkeyRSAExponentLiteral·TestCase
description
In the current ontology we have moved to literals as the standard way of describing modulus and exponents
title
rsa:exponent key is a literal
pubkeyRSAExponentOldFunctional·TestCase
title
if exponent is using non literal notation, there should be only one cert:decimal relation to plain literal
pubkeyRSAModulus·TestRequirement
title
rsa:modulus is well formed
pubkeyRSAModulusFunctional·TestCase
description
More than one modulus if they don't convert to the same number will lead to erratic behavior (one server will choose one the other server will chose the other)
title
not more than one modulus per RSA public key - or else they have to be identical
pubkeyRSAModulusLiteral·TestCase
description
In the current ontology we have moved to literals as the standard way of describing modulus and exponents
title
rsa:modulus is a literal number
pubkeyRSAModulusOldFunctional·TestCase
note
this should be a deprecated test sooner rather than later. Warn people to move to newer notation.
title
if modulus is using non literal notation, there should be only one cert:hex relation to plain literal
webidAuthentication·TestRequirement
description
At least one webid claimed in the certificate has public key that verifies.
title
WebID Authentication Test
webidClaim·TestRequirement
description
Verification of a particular WebID claim
title
Particular WebId Claim Test