Update Share Object UI to reflect max expiration time

[cesnietor]

part of solution for: #922

Updates the UI to show the max expiration time returned from /api/v1/buckets/max-share-exp API.
It also adds some documentation on how that works.

Before:

After:

Test Steps:

• Within Console running in dev mode
• Set env variable CONSOLE_STS_DURATION value to 25h40m
• Run server like:

make && CONSOLE_ACCESS_KEY=minioconsole
CONSOLE_SECRET_KEY=minioconsole
CONSOLE_MINIO_SERVER=http://localhost:9000
CONSOLE_DEV_MODE=on CONSOLE_STS_DURATION=25h40m ./console server

In the console UI with an existing bucket with an object:

• click Share
• Modal should open allowing only to set the date specified by the env variable

To TEST full integration:

• generate assets
• make assets
• build console with minio https://github.com/minio/console/blob/master/DEVELOPMENT.md#building-with-minio
• Run make build && MINIO_STS_DURATION=15m ./minio server ~/Data (the min allowed duration is 15 min) less than that it will return an invalid duration error.
• Login
• With an uploaded object click share and change the time to your preferred value.
• The object should expire if the UI session expires (15 min after logging in) or after the selected expiration value
• The UI shouldn't allow you to set more than the value set in the env variable

To TEST with IDP no env:

• configure the IDP
• Don't define the env variable
• Share link max allowed exp time would be 12h in the UI
• Share link should expire when it reaches the IDP expiration time

To TEST with IDP with env:

• configure the IDP
• define the env variable
• Share link max allowed exp time would be the value of the env variable in the UI
• Share link should expire when it reaches the env variable expiration time, not the one from the IDP.

[jinapurapu]

Is it a concern that the bucketName and objectName (Key and Resource) are displayed after link expiration?

[cesnietor]

Is it a concern that the bucketName and objectName (Key and Resource) are displayed after link expiration?

@jinapurapu they are encoded in the url anyways so it's ok.

[ravindk89]

Two suggested patterns @cesnietor (Forgot to hit Comment yesterday 😓 )

#. Show Max Possible Time

The following URL lets you share this object without requiring a login.
The URL expires automatically at the earlier of your configured time (1D and 1H and 1M) or the expiration of your current web session.

TOOLTIP
You can reset your session by logging out and logging back in to the web UI.
You can increase the maximum configuration time by setting the MINIO_STS_DURATION environment variable on all your nodes.
You can use mc share as an alternative to this UI, where the session length does not limit the URL validity.

#. Show Remaining Session Time

The following URL lets you share this object without requiring a login.
The URL expires automatically at the earlier of your configured time (1D and 1H and 1M) or the expiration of your current web session (1H and 1M).

TOOLTIP
You can reset your session by logging out and logging back in to the web UI.
You can increase the maximum configuration time by setting the MINIO_STS_DURATION environment variable on all your nodes.
You can use mc share as an alternative to this UI, where the session length does not limit the URL validity.

[cesnietor]

@ravindk89 I've updated the PR using the first proposal and looks good. Thanks.

[bexsoft]

LGTM