Couldn't authenticate with UserNameWSTrustBinding_IWSTrust13Async in "Federation" mode about php-crm-toolkit HOT 10 CLOSED

Yeah I'll have a look for now I've just patched it locally to make it work... if I remember correctly it did return something just that it was error-ing out.

"An error occured when verifying security for the message" but the moment I switched to Async2 it connected right away.

from php-crm-toolkit.

@wizardist There you go

from php-crm-toolkit.

Hi @meuhland

this does not look like a standard binding. What version of ADFS are you running? Do you know if any adjustments have been made to the claims?

Cheers
George

from php-crm-toolkit.

ADFS running on Windows 2016 that might be why I was having issues then.

from php-crm-toolkit.

@meuhland

interesting... We're focusing our efforts on OAuth in the next release so might have overlooked 2016 server. Can you figure out how to detect and add an if around that code? If not, can you send us a copy of the full wsdl so that we could try figuring out how to branch for Windows 2016 server?

Thanks
George

from php-crm-toolkit.

@meuhland

Oh, perhaps, we could just try UserNameWSTrustBinding_IWSTrust13Async2 if UserNameWSTrustBinding_IWSTrust13Async returns nothing? Can you validate that and send us a pull request?

from php-crm-toolkit.

@meuhland could you give me a list of enabled token endpoints in your AD FS? Endpoints of interest are username, usernamebasictransport and usernamemixed.

from php-crm-toolkit.

@wizardist From where would you get those... I'm drawing a blank.

from php-crm-toolkit.

@meuhland something like this: https://i.stack.imgur.com/VCqP4.png

On a different installation there's a very similar issue, only UserNameWSTrustBinding_IWSTrust13Async1 is the correct port name. I'd like to confirm.

from php-crm-toolkit.

@meuhland could you test the latest version against your deployment? Should be fixed.

from php-crm-toolkit.