Petteri Stenius

I run into this issue when hosting my oidc client web app on localhost using plain http not https. I guess this use case is quite common while developing a...

There are valid use cases that do work with the default SameSite=Lax policy for the nonce cookie. For example OIDC authorization code flow using top-level redirects and http get method...

Ok, thank you. That's good to know.

Hi. I have seen this error when there is an other process listening on the same TCP port. Maybe you have left behind a previous "kli witness start" process as...

Hi @daidoji Here's a simple solution that avoids changes to the hio component. Implement a catch errors early strategy by adding a test with `server.reopen` to see if this process...

There may be some more interop issues with the http message signature implementation of keria/signify. I have reported some findings here https://github.com/WebOfTrust/keria/issues/35

Keripy definition for numbers from [Number](https://github.com/WebOfTrust/keripy/blob/86c50b466f3fb6b8a55615ce40ba1cc31d10b749/src/keri/core/coring.py#L1572C15-L1572C15): > Parameters: > num (int | str | None): non-negative int number or hex str of int > number or 0 if None >...

Hi @nkongsuwan. I have run into this same issue. I have not created a PR yet, but I have a quick and dirty fix that adds two parameters to `IssueCredentialArgs`...

Hi @nkongsuwan. I have not seen any lmdb issues in my test setup in a long time. When I did, I was usually able to trace things back to my...

There's a client side workaround for this in the integration tests https://github.com/WebOfTrust/signify-ts/blob/6574f3089fdc95abd52ff08b43f569107ec1009f/examples/integration-scripts/utils/test-util.ts#L64-L82