You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.