Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet issues and pull requests
#1660 - IssuerSigningKeyResolver doesn't support async
Issue -
State: open - Opened by punitsinghi over 3 years ago
- 2 comments
Labels: Enhancement, Customer reported
#1654 - using JsonWebTokenHandler with ASP.NET Core (AddJwtBearer)
Issue -
State: closed - Opened by ericsampson over 3 years ago
- 7 comments
Labels: Enhancement
#1651 - Add new delegate to validate tokens being replayed that takes a token.
Issue -
State: closed - Opened by brentschmaltz over 3 years ago
- 3 comments
Labels: Internal
#1649 - Using DisposableObjectPool for AesGcm instance.
Pull Request -
State: closed - Opened by RojaEnnam over 3 years ago
#1649 - Using DisposableObjectPool for AesGcm instance.
Pull Request -
State: closed - Opened by RojaEnnam over 3 years ago
#1649 - Using DisposableObjectPool for AesGcm instance.
Pull Request -
State: closed - Opened by RojaEnnam over 3 years ago
#1649 - Using DisposableObjectPool for AesGcm instance.
Pull Request -
State: closed - Opened by RojaEnnam over 3 years ago
#1649 - Using DisposableObjectPool for AesGcm instance.
Pull Request -
State: closed - Opened by RojaEnnam over 3 years ago
#1649 - Using DisposableObjectPool for AesGcm instance.
Pull Request -
State: closed - Opened by RojaEnnam over 3 years ago
#1649 - Using DisposableObjectPool for AesGcm instance.
Pull Request -
State: closed - Opened by RojaEnnam over 3 years ago
#1649 - Using DisposableObjectPool for AesGcm instance.
Pull Request -
State: closed - Opened by RojaEnnam over 3 years ago
#1642 - Unable to obtain configuration from: '[PII is hidden. For more details, see https://aka.ms/IdentityModel/PII.
Issue -
State: closed - Opened by KunalAdu over 3 years ago
- 5 comments
Labels: Customer reported, Investigate, Question
#1641 - Extra characters at the end of encrypted JWT tokens don't prevent them from being considered valid
Issue -
State: open - Opened by kevinchalet over 3 years ago
- 5 comments
Labels: P1, Customer reported, Investigate, Bug, IdentityModel8x
#1641 - Extra characters at the end of encrypted JWT tokens don't prevent them from being considered valid
Issue -
State: closed - Opened by kevinchalet over 3 years ago
- 5 comments
Labels: P1, Customer reported, Investigate, Bug, IdentityModel8x
#1636 - Saml2 holder-of-key reading/writing inconsistency
Issue -
State: open - Opened by gislikonrad over 3 years ago
Labels: P2, Customer reported, Bug, SAML
#1636 - Saml2 holder-of-key reading/writing inconsistency
Issue -
State: open - Opened by gislikonrad over 3 years ago
Labels: P2, Customer reported, Bug, SAML
#1634 - Json Serialialization of JsonWebKey
Issue -
State: closed - Opened by jeffw-wherethebitsroam over 3 years ago
- 2 comments
Labels: Customer reported, Question
#1634 - Json Serialialization of JsonWebKey
Issue -
State: closed - Opened by jeffw-wherethebitsroam over 3 years ago
- 2 comments
Labels: Customer reported, Question
#1634 - Json Serialialization of JsonWebKey
Issue -
State: closed - Opened by jeffw-wherethebitsroam over 3 years ago
- 2 comments
Labels: Customer reported, Question
#1634 - Json Serialialization of JsonWebKey
Issue -
State: closed - Opened by jeffw-wherethebitsroam over 3 years ago
- 2 comments
Labels: Customer reported, Question
#1634 - Json Serialialization of JsonWebKey
Issue -
State: closed - Opened by jeffw-wherethebitsroam over 3 years ago
- 2 comments
Labels: Customer reported, Question
#1634 - Json Serialialization of JsonWebKey
Issue -
State: closed - Opened by jeffw-wherethebitsroam over 3 years ago
- 2 comments
Labels: Customer reported, Question
#1634 - Json Serialialization of JsonWebKey
Issue -
State: closed - Opened by jeffw-wherethebitsroam over 3 years ago
- 2 comments
Labels: Customer reported, Question
#1634 - Json Serialialization of JsonWebKey
Issue -
State: closed - Opened by jeffw-wherethebitsroam over 3 years ago
- 2 comments
Labels: Customer reported, Question
#1634 - Json Serialialization of JsonWebKey
Issue -
State: closed - Opened by jeffw-wherethebitsroam over 3 years ago
- 2 comments
Labels: Customer reported, Question
#1626 - change base type of SecurityTokenUnableToValidateException
Pull Request -
State: closed - Opened by keegan-caruso over 3 years ago
- 1 comment
#1626 - change base type of SecurityTokenUnableToValidateException
Pull Request -
State: closed - Opened by keegan-caruso over 3 years ago
- 1 comment
#1626 - change base type of SecurityTokenUnableToValidateException
Pull Request -
State: closed - Opened by keegan-caruso over 3 years ago
- 1 comment
#1626 - change base type of SecurityTokenUnableToValidateException
Pull Request -
State: closed - Opened by keegan-caruso over 3 years ago
- 1 comment
#1626 - change base type of SecurityTokenUnableToValidateException
Pull Request -
State: closed - Opened by keegan-caruso over 3 years ago
- 1 comment
#1626 - change base type of SecurityTokenUnableToValidateException
Pull Request -
State: closed - Opened by keegan-caruso over 3 years ago
- 1 comment
#1626 - change base type of SecurityTokenUnableToValidateException
Pull Request -
State: closed - Opened by keegan-caruso over 3 years ago
- 1 comment
#1626 - change base type of SecurityTokenUnableToValidateException
Pull Request -
State: closed - Opened by keegan-caruso over 3 years ago
- 1 comment
#1607 - Add option to remove the PII filtering on required fields.
Issue -
State: closed - Opened by RojaEnnam over 3 years ago
- 2 comments
Labels: Enhancement, Internal, PII / Logging
#1607 - Add option to remove the PII filtering on required fields.
Issue -
State: closed - Opened by RojaEnnam over 3 years ago
- 2 comments
Labels: Enhancement, Internal, PII / Logging
#1607 - Add option to remove the PII filtering on required fields.
Issue -
State: closed - Opened by RojaEnnam over 3 years ago
- 2 comments
Labels: Enhancement, Internal, PII / Logging
#1607 - Add option to remove the PII filtering on required fields.
Issue -
State: closed - Opened by RojaEnnam over 3 years ago
- 2 comments
Labels: Enhancement, Internal, PII / Logging
#1607 - Add option to remove the PII filtering on required fields.
Issue -
State: closed - Opened by RojaEnnam over 3 years ago
- 2 comments
Labels: Enhancement, Internal, PII / Logging
#1607 - Add option to remove the PII filtering on required fields.
Issue -
State: closed - Opened by RojaEnnam over 3 years ago
- 2 comments
Labels: Enhancement, Internal, PII / Logging
#1607 - Add option to remove the PII filtering on required fields.
Issue -
State: closed - Opened by RojaEnnam over 3 years ago
- 2 comments
Labels: Enhancement, Internal, PII / Logging
#1607 - Add option to remove the PII filtering on required fields.
Issue -
State: closed - Opened by RojaEnnam over 3 years ago
- 2 comments
Labels: Enhancement, Internal, PII / Logging
#1607 - Add option to remove the PII filtering on required fields.
Issue -
State: closed - Opened by RojaEnnam over 3 years ago
- 2 comments
Labels: Enhancement, Internal, PII / Logging
#1607 - Add option to remove the PII filtering on required fields.
Issue -
State: closed - Opened by RojaEnnam over 3 years ago
- 2 comments
Labels: Enhancement, Internal, PII / Logging
#1607 - Add option to remove the PII filtering on required fields.
Issue -
State: closed - Opened by RojaEnnam over 3 years ago
- 2 comments
Labels: Enhancement, Internal, PII / Logging
#1607 - Add option to remove the PII filtering on required fields.
Issue -
State: closed - Opened by RojaEnnam over 3 years ago
- 2 comments
Labels: Enhancement, Internal, PII / Logging
#1607 - Add option to remove the PII filtering on required fields.
Issue -
State: closed - Opened by RojaEnnam over 3 years ago
- 2 comments
Labels: Enhancement, Internal, PII / Logging
#1603 - IDX10511 and IDX10634 errors when using custom JWT Bearer with AzureAD Bearer
Issue -
State: open - Opened by udlose over 3 years ago
- 13 comments
Labels: Customer reported, Investigate, Question, PII / Logging
#1601 - ConfigurationManager.GetConfigurationAsync() doesn't return JsonWebKeySet in 6.8.0
Issue -
State: closed - Opened by arianmotamedi over 3 years ago
- 8 comments
Labels: Customer reported, Investigate
#1598 - JwtRegisteredClaimNames Missing Standard OpenIdConnect claims
Issue -
State: closed - Opened by apsthisdev over 3 years ago
- 2 comments
Labels: Enhancement, Customer reported
#1598 - JwtRegisteredClaimNames Missing Standard OpenIdConnect claims
Issue -
State: open - Opened by apsthisdev over 3 years ago
- 2 comments
Labels: Enhancement, Customer reported
#1598 - JwtRegisteredClaimNames Missing Standard OpenIdConnect claims
Issue -
State: open - Opened by apsthisdev over 3 years ago
- 2 comments
Labels: Enhancement, Customer reported
#1598 - JwtRegisteredClaimNames Missing Standard OpenIdConnect claims
Issue -
State: open - Opened by apspi over 3 years ago
- 1 comment
Labels: Enhancement, Customer reported
#1598 - JwtRegisteredClaimNames Missing Standard OpenIdConnect claims
Issue -
State: open - Opened by apsthisdev over 3 years ago
- 2 comments
Labels: Enhancement, Customer reported
#1598 - JwtRegisteredClaimNames Missing Standard OpenIdConnect claims
Issue -
State: open - Opened by apspi over 3 years ago
- 1 comment
Labels: Enhancement, Customer reported
#1598 - JwtRegisteredClaimNames Missing Standard OpenIdConnect claims
Issue -
State: open - Opened by apsthisdev over 3 years ago
- 2 comments
Labels: Enhancement, Customer reported
#1598 - JwtRegisteredClaimNames Missing Standard OpenIdConnect claims
Issue -
State: closed - Opened by apsthisdev over 3 years ago
- 2 comments
Labels: Enhancement, Customer reported
#1598 - JwtRegisteredClaimNames Missing Standard OpenIdConnect claims
Issue -
State: open - Opened by apspi over 3 years ago
- 1 comment
Labels: Enhancement, Customer reported
#1598 - JwtRegisteredClaimNames Missing Standard OpenIdConnect claims
Issue -
State: closed - Opened by apsthisdev over 3 years ago
- 2 comments
Labels: Enhancement, Customer reported
#1595 - Adding the IDisposable interface to ECDsaSecurityKey, RsaSecurityKey and X509SecurityKey
Pull Request -
State: closed - Opened by mafurman over 3 years ago
- 2 comments
#1595 - Adding the IDisposable interface to ECDsaSecurityKey, RsaSecurityKey and X509SecurityKey
Pull Request -
State: closed - Opened by mafurman over 3 years ago
- 2 comments
#1595 - Adding the IDisposable interface to ECDsaSecurityKey, RsaSecurityKey and X509SecurityKey
Pull Request -
State: closed - Opened by mafurman over 3 years ago
- 2 comments
#1595 - Adding the IDisposable interface to ECDsaSecurityKey, RsaSecurityKey and X509SecurityKey
Pull Request -
State: closed - Opened by mafurman over 3 years ago
- 2 comments
#1595 - Adding the IDisposable interface to ECDsaSecurityKey, RsaSecurityKey and X509SecurityKey
Pull Request -
State: closed - Opened by mafurman over 3 years ago
- 2 comments
#1595 - Adding the IDisposable interface to ECDsaSecurityKey, RsaSecurityKey and X509SecurityKey
Pull Request -
State: closed - Opened by mafurman over 3 years ago
- 2 comments
#1595 - Adding the IDisposable interface to ECDsaSecurityKey, RsaSecurityKey and X509SecurityKey
Pull Request -
State: closed - Opened by mafurman over 3 years ago
- 2 comments
#1594 - Saml2SignatureValidation fails to validate document which is considered valid by online validators
Issue -
State: open - Opened by madelson over 3 years ago
- 4 comments
Labels: Customer reported, Investigate, Bug, P3
#1594 - Saml2SignatureValidation fails to validate document which is considered valid by online validators
Issue -
State: open - Opened by madelson over 3 years ago
- 4 comments
Labels: Customer reported, Investigate, Bug, P3
#1594 - Saml2SignatureValidation fails to validate document which is considered valid by online validators
Issue -
State: open - Opened by madelson over 3 years ago
- 4 comments
Labels: Customer reported, Investigate, Bug, P3
#1594 - Saml2SignatureValidation fails to validate document which is considered valid by online validators
Issue -
State: open - Opened by madelson over 3 years ago
- 4 comments
Labels: Customer reported, Investigate, Bug, P3
#1583 - Using DefaultAzureCredential (new Azure SDK) with ManagedKeyVaultSecurityKey not possible?
Issue -
State: closed - Opened by aKzenT over 3 years ago
- 13 comments
Labels: Customer reported, Investigate
#1582 - Check if Exp and Nbf values exist.
Pull Request -
State: closed - Opened by RojaEnnam over 3 years ago
- 1 comment
#1582 - Check if Exp and Nbf values exist.
Pull Request -
State: closed - Opened by RojaEnnam over 3 years ago
- 1 comment
#1582 - Check if Exp and Nbf values exist.
Pull Request -
State: closed - Opened by RojaEnnam over 3 years ago
- 1 comment
#1582 - Check if Exp and Nbf values exist.
Pull Request -
State: closed - Opened by RojaEnnam over 3 years ago
- 1 comment
#1582 - Check if Exp and Nbf values exist.
Pull Request -
State: closed - Opened by RojaEnnam over 3 years ago
- 1 comment
#1582 - Check if Exp and Nbf values exist.
Pull Request -
State: closed - Opened by RojaEnnam over 3 years ago
- 1 comment
#1582 - Check if Exp and Nbf values exist.
Pull Request -
State: closed - Opened by RojaEnnam over 3 years ago
- 1 comment
#1582 - Check if Exp and Nbf values exist.
Pull Request -
State: closed - Opened by RojaEnnam over 3 years ago
- 1 comment
#1582 - Check if Exp and Nbf values exist.
Pull Request -
State: closed - Opened by RojaEnnam over 3 years ago
- 1 comment
#1574 - Resource parameter for OIDC/OAuth authorize request has wrong format
Issue -
State: open - Opened by leastprivilege over 3 years ago
- 8 comments
Labels: Enhancement, Customer reported
#1574 - Resource parameter for OIDC/OAuth authorize request has wrong format
Issue -
State: open - Opened by leastprivilege over 3 years ago
- 8 comments
Labels: Enhancement, Customer reported
#1574 - Resource parameter for OIDC/OAuth authorize request has wrong format
Issue -
State: open - Opened by leastprivilege over 3 years ago
- 8 comments
Labels: Enhancement, Customer reported
#1574 - Resource parameter for OIDC/OAuth authorize request has wrong format
Issue -
State: open - Opened by leastprivilege over 3 years ago
- 15 comments
Labels: Enhancement, Customer reported
#1574 - Resource parameter for OIDC/OAuth authorize request has wrong format
Issue -
State: open - Opened by leastprivilege over 3 years ago
- 15 comments
Labels: Enhancement, Customer reported
#1557 - Changing XmlUtil.GetXsiTypeAsQualifiedName to retrieve the attribute …
Pull Request -
State: closed - Opened by henrik-me almost 4 years ago
- 2 comments
#1557 - Changing XmlUtil.GetXsiTypeAsQualifiedName to retrieve the attribute …
Pull Request -
State: closed - Opened by henrik-me almost 4 years ago
- 2 comments
#1557 - Changing XmlUtil.GetXsiTypeAsQualifiedName to retrieve the attribute …
Pull Request -
State: closed - Opened by henrik-me almost 4 years ago
- 2 comments
#1557 - Changing XmlUtil.GetXsiTypeAsQualifiedName to retrieve the attribute …
Pull Request -
State: closed - Opened by henrik-me almost 4 years ago
- 2 comments
#1557 - Changing XmlUtil.GetXsiTypeAsQualifiedName to retrieve the attribute …
Pull Request -
State: closed - Opened by henrik-me almost 4 years ago
- 2 comments
#1557 - Changing XmlUtil.GetXsiTypeAsQualifiedName to retrieve the attribute …
Pull Request -
State: closed - Opened by henrik-me almost 4 years ago
- 2 comments
#1557 - Changing XmlUtil.GetXsiTypeAsQualifiedName to retrieve the attribute …
Pull Request -
State: closed - Opened by henrik-me almost 4 years ago
- 2 comments
#1557 - Changing XmlUtil.GetXsiTypeAsQualifiedName to retrieve the attribute …
Pull Request -
State: closed - Opened by henrik-me almost 4 years ago
- 2 comments
#1557 - Changing XmlUtil.GetXsiTypeAsQualifiedName to retrieve the attribute …
Pull Request -
State: closed - Opened by henrik-me almost 4 years ago
- 2 comments
#1557 - Changing XmlUtil.GetXsiTypeAsQualifiedName to retrieve the attribute …
Pull Request -
State: closed - Opened by henrik-me almost 4 years ago
- 2 comments
#1547 - Token validation does not use require audience parameter
Issue -
State: open - Opened by DaveBrue almost 4 years ago
- 5 comments
Labels: P2, Customer reported, Bug
#1542 - Validation of JWT based on the x5c header field is not working
Issue -
State: closed - Opened by RufusJWB almost 4 years ago
- 10 comments
Labels: Customer reported, Question
#1542 - Validation of JWT based on the x5c header field is not working
Issue -
State: closed - Opened by RufusJWB almost 4 years ago
- 10 comments
Labels: Customer reported, Question
#1542 - Validation of JWT based on the x5c header field is not working
Issue -
State: closed - Opened by RufusJWB almost 4 years ago
- 10 comments
Labels: Customer reported, Question
#1542 - Validation of JWT based on the x5c header field is not working
Issue -
State: closed - Opened by RufusJWB almost 4 years ago
- 10 comments
Labels: Customer reported, Question
#1533 - WriteXmlnsAttribute in DelegatingXmlDictionaryWriter throws exception
Issue -
State: closed - Opened by gislikonrad about 4 years ago
- 3 comments
Labels: Customer reported, Bug