-
Great library!
The one missing feature that's luring me over to the [dark side](https://github.com/ciaranj/connect-auth) is the ability to serve as an oAuth provider instead of a consumer.
Once I'm …
-
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Description
The Azure Enterprise Scale repository includes a policy initiative called [*Enforce recommended gu…
-
### Title: Associate ORCID with Existing User Accounts
As an existing user,
I want to associate my ORCID with my current account,
So that I can transition to using ORCID for future logins.
Accepta…
-
We support both `jwks` and `jwks_uri` in client-metadata. When I was experimenting, the `jwks` ("inline" keys in the client-metadata document itself) didn't work though. I can see there is code for it…
-
# Feature request
Currently, only the provider_token (oauth_token) is being returned for OAuth1.0 providers. In the future, we would either want to return the `oauth_secret_token` as well or not at a…
-
**Describe the bug**
When you have OAuth provider to authenticate your application AND saml **source** user can't complete the flow via SAML because at the very end they will be redirected to Authent…
-
**Describe the bug**
Context: I am creating a custom [declarative agent](https://learn.microsoft.com/en-us/microsoft-365-copilot/extensibility/build-declarative-agents?tabs=ttk) with an existing API …
-
**Describe the bug**
smallrye-jwt seems to fetch keys from the OAuth provider's key endpoint only on first request, however if this original fetch fails, the library never retries, and all subsequent…
-
**Describe the bug**
When a consumer's connection outlives its SASL authentication (in this case an OAuth token), then consumer will fail to fetch new records because the broker no longer accepts any…
-
The first version could be only setting up custom OAuth providers, being able to set all its fields should be enough (see screenshot bellow).
But the ideal implementation for me should be being abl…