Jay Modi f5cd833af4 Use epoch millis for token expiration instead of ZonedDateTime (elastic/x-pack-elasticsearch#1417) ...

For user tokens, we were storing the expiration time as a date with the date time format in the
mappings. Occasionally, we would get CI failures due to parsing the date and having an invalid
format. This change simplifies the user tokens to simply use an Instant and convert it to the epoch
millis when we index the document. This eliminates the need for a date formatter and should ensure
we no longer have issues with parsing the dates.

Additionally, the TokenAuthIntegTests#testExpireMultipleTimes could fail if the token was expired
but the approximation for the expiration time was after the current time. In order to resolve this
we get the exact expiration time from the token and use that in the test.

relates elastic/x-pack-elasticsearch#1255

Original commit: elastic/x-pack-elasticsearch@d4bf53e7bc

2017-05-15 14:20:12 -06:00

..

bin/x-pack

Rename core plugin and transport dirs

2017-02-10 11:02:42 -08:00

bwc-zip

Build: Build 5.x version of xpack for bwc tests to use (elastic/x-pack-elasticsearch#885)

2017-04-07 22:19:30 -07:00

config/x-pack

Rename core plugin and transport dirs

2017-02-10 11:02:42 -08:00

keys

Rename core plugin and transport dirs

2017-02-10 11:02:42 -08:00

licenses

Update Netty to 4.1.11.Final

2017-05-12 15:54:05 -04:00

src

Use epoch millis for token expiration instead of ZonedDateTime (elastic/x-pack-elasticsearch#1417)

2017-05-15 14:20:12 -06:00

build.gradle

Adapt x-pack after the parent/child modularisation (elastic/x-pack-elasticsearch#1407)

2017-05-12 15:59:40 +02:00