expiring-password-intercept-config.xml -- time_t format?

[Cantor, Scott]

On 3/17/17, 11:57 PM, "users on behalf of Paul B. Henson" <users-bounces at shibboleth.net on behalf of henson at cpp.edu> wrote:

> I'm currently looking at idp 3.3.1 and planning an upgrade, and was
> wondering if there's a way to make the built-in password expiration
> function support an attribute with a date stored in unix time_t format?

Other than just a RFE, probably by supplying an alternative condition bean or maybe by converting the data in the resolver into a string that the supplied condition can parse. A scripted attribute could probably convert the epoch string into a formatted string and make that the value of the attribute.

> I poked around the org.joda.time.format.DateTimeFormat
> documentation and nothing jumped out.

The date predicate was probably too limited in assuming a formatter would be needed. I just built what I needed at the time because the whole condition bean can be replaced.

> It looks like it would be cool to
> turn on if all it takes is some configuration, but probably not worth
> having to write my own java code to make it happen :).

I think you'll find it's a good practice to create an "extension" project to put odds and ends you might need in Java so that when things come up, you just have to throw together a Java class and rebuild/redeploy. It seems like a hassle when you have to start a project from scratch, but adding a class to an existing project is pretty simple.

I think we'll probably look at providing something like that in the distribution for people.

-- Scott