Translations for loa-condition-level and loa-max-age
closes #29738 Signed-off-by: mposolda <mposolda@gmail.com>
This commit is contained in:
parent
9d16f0e7c0
commit
bb5f308e1d
1 changed files with 4 additions and 0 deletions
|
@ -2987,6 +2987,10 @@ authenticatorRefConfig.value.help=Add a custom reference name for the authentica
|
|||
authenticatorRefConfig.value.label=Authenticator Reference
|
||||
authenticatorRefConfig.maxAge.help=The max age in seconds that the authenticator reference value is good for in an SSO session. When the Authentication Method Reference (AMR) protocol mapper is used, the AMR will only be considered valid and populated in the token if the authenticator execution was completed within the specified max age.
|
||||
authenticatorRefConfig.maxAge.label=Authenticator Reference Max Age
|
||||
loa-condition-level=Level of Authentication (LoA)
|
||||
loa-condition-level.tooltip=Level of authentication. This value should be always integer, which is greater or equal to 0. The subflows in the authentication flow should be always ordered from lowest levels to a higher levels.
|
||||
loa-max-age=Max Age
|
||||
loa-max-age.tooltip=Maximum age in seconds for this level of authentication to be valid. If the particular level is requested and user already authenticated with this level earlier than specified amount of seconds ago, he will not be asked to re-authenticate. But if he authenticated later than specified amount of seconds ago, he will need to re-authenticate with this level again. Value 0 in the configuration means that user is always required to re-authenticate with this level whenever this level is requested.
|
||||
includeInLightweight.label=Add to lightweight access token
|
||||
includeInLightweight.tooltip=Should the claim be added to the lightweight access token?
|
||||
lightweightAccessToken=Always use lightweight access token
|
||||
|
|
Loading…
Reference in a new issue