In reply to @boyan.tsolov:vereign.com

There seems to be an issue with the credential definition itself. Use this one as a substitute:

BsfUfTECZPVRnoCgHUfB3p:3:CL:72211:Smart-X-Member-Cred-Def

boyan.tsolov: this subtitute one giving 404 now.

curl --location 'https://ssi-dev.vereign.com/ocm-ui/attestation/v1/credentialDef?schemaID=BsfUfTECZPVRnoCgHUfB3p%3A3%3ACL%3A72211%3ASmart-X-Member-Cred-Def'
--header 'accept: application/json'

[https://ssi-dev.vereign.com/ocm-ui/attestation/v1/create-offer-credential]

Request for offer credentials {"connectionId":"df3ae9ea-XXXX-4526-a073-2aaa0355b080","credentialDefinitionId":"BsfUfTECZPVRnoCgHUfB3p:3:CL:72211:Smart-X-Member-Cred-Def","comment":"Login with Smart-X","attributes":[{"name":"name","value":"gaiax"},{"name":"email","value":"ronak.thacker+22@XXX.com"}],"autoAcceptCredential":"never"}

:"{"message":"Request failed with status code 404","name":"Error","stack":"Error: Request failed with status code 404\n ... (1866 bytes)]

Due that again my app goes down.
2nd time facing issue in credentialDef

In reply to @thackerronak:matrix.org

boyan.tsolov: this subtitute one giving 404 now.

curl --location 'https://ssi-dev.vereign.com/ocm-ui/attestation/v1/credentialDef?schemaID=BsfUfTECZPVRnoCgHUfB3p%3A3%3ACL%3A72211%3ASmart-X-Member-Cred-Def'
--header 'accept: application/json'

In reply to @cristinapauna:matrix.org
We are in the process of adjusting to the new infra, but yes we plan to publish container images (not sure about helm yet). They will not be in a gitlab registry though, since Eclipse does not have support for that. The final landing place is still tbd

It was working until Friday for already installed apps.

I‘m at the Merlot Konsortium meeting and we tried to show the SSI Log in with the PCM App to our whole Konsortium, and nobody could access the app. BIG time embarrassing :(
If Kalin Canov you can find what’s not working, I would be so delighted! Ping me or Tim for follow up! Thank you!

In reply to @lenasauermann:matrix.org
Hi, we are currently trying to get a Gaia-X compliant ServiceOffering with our own DID-solution (with LetsEncryt certificate chain) but keep getting weird errors we don't understand...

We use the Wizard with the Gaia-X environment in the main version. We have our legalPerson and termsAndConditions VC signed with our own did/private key and a legalRegistrationNumber VC signed from the Gaia-X notary.
In the ServiceOffering VC we then link our did:web in the "providedBy" attribute field. The rest of the fields like policy, termsAndConditions and dataAccountExport we leave as provided in the example in the playground tab. When then calling the compliance service with a VP containing all four vc, we get a big error regarding Shapes, datatypes and "Less than 1 values".

Is it right that the providedBy attributes contains the did:web?

What also could cause these problems? Our participant (with the same legalPerson, termsAndConditions and legalRegistrationNumber) is accepted by the Compliance Service.