Netflix Shiro Pull Need #952

https://stash.corp.netflix.com/projects/CME/repos/shiro/pull-requests/952

This kind of pull request provides support for typically the --max-age and --max-stale red flags to the shiro command.

The --max-age flag identifies the maximum age of an appropriate token. If the token is older compared to the specified age, it will be refreshed.

The --max-stale flag specifies the particular maximum stale era of the appropriate token. If the token is boring for more than the specified grow older, it will end up being refreshed.

These flags could be helpful for controlling the consistency of token refreshes. For illustration, when you set the particular --max-age banner to 1 hours, the token will certainly be refreshed just about every hour. If an individual set the --max-stale flag to 30 minutes, typically the token will become refreshed every single 35 minutes.

To use these kinds of flags, basically put them to the shiro command word. For illustration:

 shiro --max-age 1h --max-stale 30m

This order will cause typically the shiro command word to renew the particular token every hour or so, or if that is stale for more than 25 minutes.

Benefits of making these flags

There are several benefits for you to using the --max-age and --max-stale flags:

Improved functionality: By simply handling the frequency involving token refreshes, anyone can improve typically the performance of your own application.
Reduced security risks: By refreshing bridal party regularly, you might reduce the risk of your app being sacrificed by means of a taken or out of date token.
Easier supervision: By simply centralizing the managing of token refreshes, you can help make this easier in order to manage your application's safety.

Conclusion

The --max-age and --max-stale flags are generally the valuable addition to the shiro command. They will allow you to control the consistency of token refreshes, which can improve performance, reduce security risks, and help make management easier.