The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

disable usage of verify-password=false

John A.
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 28, 2017

Hi--

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?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
lpater
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 25, 2017

Hi John,

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.

TAGS
AUG Leaders

Atlassian Community Events