Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,555,446
Community Members
 
Community Events
184
Community Groups

disable usage of verify-password=false

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

0 votes
lpater
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events