The Shibboleth IdP V4 software has reached its End of Life and is no longer supported. This documentation is available for historical purposes only. See the IDP5 wiki space for current documentation on the supported version.

DateTimeAttributeDefinition

Owned by Scott Cantor
Last updated: May 02, 2023
1 min read

This feature requires V4.3 of the IdP software.

Namespace: urn:mace:shibboleth:2.0:resolver
Schema: http://shibboleth.net/schema/idp/shibboleth-attribute-resolver.xsd

Overview

The DateTime AttributeDefinition converts one or more input values into a Java Instant (an unambiguous timestamp based on the Unix epoch) . The resulting attribute's values are of type DateTimeAttributeValue. This definition type can convert string values that are either numeric, or that match a supplied DateTimeFormatter formatting string. Numeric values may be processed in seconds or in milliseconds since the Unix epoch. It is allowed to mix numeric and formatted string inputs.

Errors in converting data may be fatal or ignored.

Reference

The following are supported:

Name

Type

Default

Description

Name

Type

Default

Description

ignoreConversionErrors

Boolean

false

If the resulting IdPAttribute has fewer values than the number of input values, then the definition will raise a fatal error by default unless this setting is changed

epochInSeconds

Boolean

true

The default is to process numeric data as seconds since the epoch, in keeping with common usage on many platforms, but if false, milliseconds are used instead, as is typical in Java

formattingString

String

 

A pattern used to create a DateTimeFormatter object to apply to non-numeric String data input to the definition

Examples

<AttributeDefinition id="expirationOfSomething" xsi:type="DateTime" epochInSeconds="false"> <InputAttributeDefinition ref="expTimeFromDirectory" /> </AttributeDefinition>

Â