All work
- Possible bug in setting clientId from properties fileJOIDCRP-71Philip Smart
- Custom c14n flow descriptor bean needs to use parent beanJOIDCRP-70Resolved issue: JOIDCRP-70Philip Smart
- Claim sanitization fails with ill behaving OPJOIDCRP-68Resolved issue: JOIDCRP-68Philip Smart
- RP 2.0.0 distribution package contains shib-support libraryJOIDCRP-57Resolved issue: JOIDCRP-57Philip Smart
- Translate nonexistent ACR in responsesJOIDCRP-51Philip Smart
- Remove failIfResourceIsNull from default asymmetric key configJOIDCRP-48Philip Smart
- Convert HTTP client executeOpen calls to ResponseHandlersJOIDCRP-46Resolved issue: JOIDCRP-46Philip Smart
- Leaks in HTTP response handlingJOIDCRP-45Resolved issue: JOIDCRP-45Philip Smart
- Null Handling TaskJOIDCRP-44Resolved issue: JOIDCRP-44Philip Smart
- Support a prompt parameter profile overrideJOIDCRP-38Philip Smart
- Add RP specific clockSkew property for IssuedAtClaimsValidatorJOIDCRP-36Resolved issue: JOIDCRP-36Philip Smart
- Add support for passive inbound requestsJOIDCRP-35Resolved issue: JOIDCRP-35Philip Smart
- Remove nonBrowser authentication flow supportJOIDCRP-34Resolved issue: JOIDCRP-34Philip Smart
- Typo in add default principals propertyJOIDCRP-33Resolved issue: JOIDCRP-33Philip Smart
- Save Access Token and Refresh Token to credential setJOIDCRP-26Resolved issue: JOIDCRP-26Philip Smart
- Add JWT Encryption Parameter Resolver SupportJOIDCRP-17Resolved issue: JOIDCRP-17Philip Smart
- Add a relying party signing parameters resolverJOIDCRP-16Resolved issue: JOIDCRP-16Philip Smart
- Support Request Object by ValueJOIDCRP-15Resolved issue: JOIDCRP-15Philip Smart
- Improve scope resolution for Authentication RequestsJOIDCRP-10Resolved issue: JOIDCRP-10Philip Smart
- OIDC login flow - appropriate use of NimbusJOIDCRP-8Resolved issue: JOIDCRP-8
- OIDC login flow - metadata use/mgmtJOIDCRP-7Resolved issue: JOIDCRP-7
- OIDC login flow - HTTP Client useJOIDCRP-6Resolved issue: JOIDCRP-6
- OIDC login flow - multiplex the RP configuration settingsJOIDCRP-5Resolved issue: JOIDCRP-5
- OIDC login flow - code cleanupJOIDCRP-4Resolved issue: JOIDCRP-4Philip Smart
- Login flow for OIDC authenticationJOIDCRP-3Resolved issue: JOIDCRP-3Philip Smart
- Convert JWT signature verification to oidc-commonsJOIDCRP-2Resolved issue: JOIDCRP-2
- Convert JWT validation to oidc-common libraryJOIDCRP-1Resolved issue: JOIDCRP-1Philip Smart
V4 Deprecation work - Attribute Resolver
Description
Environment
Details
Details
Details
Activity
Rod WiddowsonMay 23, 2019 at 2:32 PM
I'm bored with this case so I'm going to resolve and close it.
It was left open for far too many odds and sods and the time has come to enter a new case if we find something new.
The only open AI (is to do with Java7/V2 support for scripted attributes for which I have entered
Rod WiddowsonMay 17, 2019 at 1:15 PM
IdPAttributeValue rework complete.
Rod WiddowsonMay 13, 2019 at 3:00 PM
Moved into
Rod WiddowsonMay 12, 2019 at 11:58 AM
... it's coming by default from the dist/webapp/ tree, right?
Absolutely the only comaptibilitywe might care about is someone deploying their on jsp on top. Id forgotten about the metrics so I find myself not really caring about people whose jsp pages break (jsp is programming, this is a maor release its an API change live with it).
I'm getting quietenamoured with the getReloadableSubsystems() think. I'll give it a bash and see what it looks like.
Scott CantorMay 11, 2019 at 8:01 PM
I don't really think we need to worry about people changing the status page much, the metrics were really meant to be the "supportable" interface to the information. I think we actually do overwrite that content, since it's coming by default from the dist/webapp/ tree, right?
Starting to pull together a lit of things to get rid of in V4 for Attribute Definition
1) the :ad and :dc namespaces
2) The need to warn/fail if we encounter <Dependency> (or related) children (StaticDataConnector, ContextDerivivedAttribute, SupbjectDerivedAttribute)