Netflix Shiro Pull Request #952
https://stash.corp.netflix.com/projects/CME/repos/shiro/pull-requests/952
This pull request provides support for the particular --max-age in addition to --max-stale red flags to the shiro command.
The --max-age flag identifies the maximum era of an appropriate token. If the token is older as compared to the specified grow older, it will always be refreshed.
The --max-stale flag specifies the maximum stale time of some sort of valid token. If the particular token is dull for more compared to the specified grow older, it will be refreshed.
These flags can be useful regarding controlling the regularity of token refreshes. For example, when you set the --max-age banner to 1 hour, the token may be refreshed each hour. If you set the --max-stale flag to be able to 30 minutes, the particular token will always be refreshed every single 35 minutes.
To use these types of flags, merely include them to the particular shiro command word. For example of this:
shiro --max-age 1h --max-stale 30m This control will cause typically the shiro order to renew the particular token just about every hours, or if it is stale for more than thirty minutes.
Benefits of making these flags
There are several benefits in order to using the --max-age and --max-stale flags:
- Improved functionality: By simply maintaining the consistency of token refreshes, you can boost the particular performance of your current application.
- Reduced safety measures risks: By refreshing bridal party regularly, you will reduce the chance of your app being compromised by means of a taken or terminated token.
- Easier managing: By simply centralizing the administration of token refreshes, you can help to make that easier to deal with your application's security.
Conclusion
The --max-age and --max-stale flags are generally some sort of valuable improvement to the shiro command. These people allow you for you to control the regularity of token refreshes, which can boost performance, reduce safety risks, and create management easier.