-
3.4 Client Metadata
https://w3c-fedid.github.io/FedCM/#idp-api-client-id-metadata-endpoint
> privacy_policy_url, of type [USVString](https://webidl.spec.whatwg.org/#idl-USVString)
> A link to…
-
### Community Note
- Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the c…
-
Mellon 19.1 built from from source for httpd on RHEL8, using ./configure --enable-diagnostics, make and make install. No problems there.
SP metadata, generated using the provided generate-metadata…
xldcx updated
1 month ago
-
### Preflight Checklist
- [X] I could not find a solution in the existing issues, docs, nor discussions
- [X] I have joined the [ZITADEL chat](https://zitadel.com/chat)
### Describe your proble…
-
## Description
The team would like to utilize GitHub as the Identity Provider (IdP) for any argocd instance that is created. In order to do this, the team will attempt to use Keycloak as the in-betwee…
-
This will be useful for two use cases:
1. at onboarding time: fix any misconfiguration without having to delete the silo
2. after onboarding: there is a need to change to another provider (though us…
-
**Expected behaviour:**
Teleport should work with Keycloak as a SAML IdP when client signature validation on Keycloak is enabled and required. The integration should allow seamless communication betw…
-
[This issue is imported from pivotal - Originaly created at Feb 13, 2023 by andreklaver](https://www.pivotaltracker.com/story/show/184461096)
We kunnen in jira doelgericht mails genereren en sturen (…
-
I have an AWS NLB with SSL offloading which sends that traffic to port 8080. The request flows through fine, but the JWT verification is not working. I would expect a 401, but get a 200 returned from …
-
**Describe the problem**
I installed Netbird with keycloak as idp. When I try to login I get the following error:
Request failed with status code 401. Error: token invalid
In docker logs:
```
…