We would like to disable the usage of the verify-password parameter in the POST usermanagement/1/session endpoint of Crowd's restful service.
We'd like to force all authentications against our Crowd service to include the authenticated user's password.
Is this possible?
The validate-password parameter of the usermanagement/1/session resource you mention is a part of Crowd's Single Sign-On protocol, and can be used by connected applications to perform user authentication without requiring the password (for example based on a remember-me cookie).
This API can only be called by an application connected to Crowd (and not normal users). Such applications are considered to be trusted, and have access to the user directories associated with them.
There is currently no way to prevent an application from using this api in Crowd itself (and it would probably affect the SSO functionality within the application). Instead you can consider disabling functionalities in the application that would use this API (like remember-me logins), to enforce authentication using a password.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot