Hi Jondric Zafra,
As you mentioned that “I’ve been able to get it to have a username, hashed password digest, nonce, and created.”, we now need to send the same manner, can you please share the policy if we have like this.
Regards,
Ravi.
Hi all,
I want to add a username token to our outgoing SOAP requests containing a username, clear(plaintext) password, nonce, and created date like below:
<wsse:UsernameToken wsu:Id=“UsernameToken”>
wsse:Username Administrator </wsse:Username>
<wsse:Password Type=“http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText ”>manage </wsse:Password>
<wsse:Nonce EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary\ ">+N5aKhsk4nK+mvU6w//HRg== </wsse:Nonce>
wsu:Created 2018-10-15T09:10:09.132Z </wsu:Created>
</wsse:UsernameToken>
Is this possible? What I’ve done so far:
Added a port alias to the consumer WSD’s binding to make the username and password configurable.
Played around with policies. I can get a username token with a username and clear password, and I’ve been able to get it to have a username, hashed password digest, nonce, and created. With IS 10.1, is this even possible, given that policies are only supporting up to WSSecurityPolicy 1.2?