Issue with WS-Security Username and Password Digest authentication

book

Article ID: 7432

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) AXIOMATICS POLICY SERVER CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On

Issue/Introduction

When we try to use  the 12.52 SP1 CR5 Web Services Security (WSS) Agent installed on WebSphere 8.5, username and password digest authentication is not working.

If we switch to plain text username and password authentication, the transaction is successful. 

Why the digest authentication doesn't work ?

Cause

There is a limitiation with Active Directory User Store. For WS-Security Password Digest Authentication Scheme,  the Authentication Scheme tries to retrieve attribute userPassword and compares the digest value that user sends a part of input request.

 

For Active Directory, UserPassword or unicodePwd attributes cannot be retrieved for security reasons.  

 

WS-Security Username Password Authentication Scheme in Siteminder currently can support only cleartext form. We cannot support the Digest form because of these security reasons.

 

Below is link from Microsoft community :

"The users' password is stored in the Active Directory on a user object in the unicodePwd attribute. This attribute can   be written under restricted conditions, but it cannot be read due to security reasons."

https://social.technet.microsoft.com/Forums/ie/en-US/63e3cf2d-f186-418e-bc85-58bdc1861aae/view-password-hash-in-active-directory?forum=winserverfiles

Environment

ProductName=CA SiteMinder Web Services Security FullVersion=12.52.105.2112

Resolution

Workaround for this issue is to use the plain text username and password Authentication Scheme (cleartext).

Additional Information

Added a comment to the WSS documentation :

https://docops.ca.com/ca-single-sign-on/12-52-sp1/en/configuring/web-services-security-wss-configuration/configure-authentication-schemes-to-verify-user-identities-obtained-from-web-service-requests/ws-security-authentication-introduced