OIDC dynamic client registration validity

[Cantor, Scott]

On 3/1/22, 11:20 AM, "users on behalf of Wessel, Keith" <users-bounces at shibboleth.net on behalf of kwessel at illinois.edu> wrote:

>    So, if the registration endpoint is paying attention to the defaultRegistrationValidity property and I'm not
> overriding that property elsewhere, then the expiration time would be calculated at the time of registration
> and saved in the expires column in the StorageRecords table for that entry, correct?

If it's non-null. I actually don't know what the default is in the code. 

> I've never touched it or changed the default. So, I have to suspect that in the past, it was somehow defaulting
> to no expiration and, possibly, that has changed?

I don't know.

>    Still doesn't explain how the entry in question disappeared last week, though, since you've already told me
> that the JPA storage service just ignores expired entries instead of deleting them.

Yes, nothing would have deleted it that I know of. Some of the storage classes have a cleanup thread but the JPA one doesn't install one that I can see.

-- Scott