THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Page properties | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Motivation
The current delegation token framework supports mainly Kerberos authentication and Hadoop based tokens. This satisfies the use cases described in FLIP-211, however there are many non-hadoop compliant frameworks, where the authentication protocol is not Kerberos. The main motivation is to generalize the actual delegation token framework to make it authentication protocol agnostic. This change would open doors to implement providers for example for S3 (amongst many others).
...
- security.delegation.tokens.renewal.retry.backoff needs to be added which falls back to has the same default value like security.kerberos.tokens.renewal.retry.backoff . Default value intended to be the same (1 hour).
- security.delegation.tokens.renewal.time-ratio needs to be added which falls back has the same default value like security.kerberos.tokens.renewal.time-ratio . Default value intended to be the same (0.75).
Compatibility, Deprecation, and Migration Plan
...