Issue Generating Credential Offer – Missing Credential Issuer Identifier

[dtsiflit]

Thank you for this repository. I've been following the instructions provided here (https://www.authlete.com/developers/oid4vci/) to interact with your issuer.

However, when I visit https://trial.authlete.net/api/offer/issue to generate a credential offer, I encounter the following error:

"An exception occurred: [A367201] A credential offer cannot be created because the identifier of the credential issuer has not been set up."

Additionally, I don’t see a QR code as expected.

Could you please provide guidance on resolving this issue? I appreciate your help and hope this is the right place to report it.

[TakahikoKawasaki]

@dtsiflit Hello. Could you tell me which example isn’t working? In the past, some configurations were accidentally removed. I'll reconfigure them.

[dtsiflit]

Hello @TakahikoKawasaki, thanks for getting back to me!

I'm encountering an error when clicking "Submit" on this page: https://trial.authlete.net/api/offer/issue.

It looks like credential_issuer is not set up and is currently null. If I recall correctly, its value was previously "https://trial.authlete.net/".

Hope this helps! Let me know if you need any additional details.

[TakahikoKawasaki]

Hmm. Other settings have also been cleared for some reason. I'll check with my engineering team.

[TakahikoKawasaki]

@dtsiflit I have quickly restored the settings, but I’m not 100% sure they are perfect. Please let me know if you still encounter any issues.

[dtsiflit]

@dtsiflit I have quickly restored the settings, but I’m not 100% sure they are perfect. Please let me know if you still encounter any issues.

@TakahikoKawasaki Sorry, I am still encountering the issue.

[TakahikoKawasaki]

@dtsiflit I reconfigured the Verifiable Credentials settings yesterday, but I found today that the values have been cleared again. I'll check with the engineering team once more. They have already identified a bug, but there may be others. Sorry for the inconvenience. The team has been updating the console UI over the past few months.

[dtsiflit]

Thank you very much, @TakahikoKawasaki !

If it helps, I first noticed this issue on Thursday (13/2), if I recall correctly. It was functioning perfectly that morning, but I encountered the issue later that afternoon.