-
### OAuth2-Proxy Version
7.5.1
### Provider
oidc
### Expected Behaviour
Option to add a custom body paramter for the /token call, for example:
/op/oidc/token
code: {{code}}
client_id: {{mono…
-
### Software versions
- **OS**: Mac OSX 14.3.1
- **Consumer Pact library**: Pact JS v12.2.0
- **Provider Pact library**: Pact JS v12.2.0
- **Node Version**: v18.18.2
### Issue Checklist
P…
-
If we're dropping the need for RVPs to specify the attester authority, we ought to mention in Phase 1 that Evidence can only be transformed an ECT about environment E only if the evidence was signed b…
-
AAL3 requires verifier impersonation resistance, as defined in Section 5.2.5.
The relevant paragraph states as follows (emphasis added)
> A verifier impersonation-resistant authentication protoc…
-
### Preflight Checklist
- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct]…
-
Hi, I am not very familiar with the principle of email address verification.
We have a new Go backend service that needs to verify the email addresses of newly registered users, and I found two re…
-
This bug is twofold. Both aspects of it originate from [rfc8616](https://tools.ietf.org/html/rfc8616#section-5), which allows d=, i=, and s= tags of a DKIM-Signature header field to be utf-8.
On t…
-
The attached CFA contains an ovious error from loc75: `__tmp_1` is assigned 0, `__VERIFIER_assert__cond` is assigned `__tmp_1` and if `__VERIFIER_assert__cond` is 0, we reach the error location. Yet, …
-
All those comparisons will be held in this thread unless an informational RFC will be created about both the status lists and the status assertions
-
When `s` is in a key's flags list, then:
> Any DKIM-Signature header fields using the "i=" tag MUST have the same domain value on the right-hand side of the "@" in the "i=" tag and the value of the…