You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The JWT auth method class uses the parameter path for the mount point in all of its methods , which strays from every other auth method which uses the name mount_point.
I think it should be consistent with the other methods.
Since it's already published as is, perhaps adding mount_point as a parameter with the same purpose and deprecating path to be removed in a future release (having both for some time) is a good path forward?
The text was updated successfully, but these errors were encountered:
Related: #644
The JWT auth method class uses the parameter
path
for the mount point in all of its methods , which strays from every other auth method which uses the namemount_point
.I think it should be consistent with the other methods.
Since it's already published as is, perhaps adding
mount_point
as a parameter with the same purpose and deprecatingpath
to be removed in a future release (having both for some time) is a good path forward?The text was updated successfully, but these errors were encountered: