-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with onsite (non dynamics.com url) installations. #5
Comments
Hi @AndyMain Have you set |
Ok I double checked, and we had an issue where the Federation authMode was not being picked up. With Federation now being used we get further but are still having issues; now getting "Could not find EndorsingSupportingTokens/Policy/IssuedToken tag in provided security policy XML vendor/alexacrm/php-crm-toolkit/src/Client.php:386" |
@AndyMain cam you give us a code fragment (after removing any sensitive info from your url)? |
Hopefully, this helps though I'm not sure, as you suggest it may be incorrect setup. I might be able to have a chat with the systems admin if anything needs to be adjusted. Let me know if you need more info. public function connect()
{
$this->clientOptions = [
'serverUrl' => $this->url,
'username' => $this->username,
'password' => $this->password,
//'authMode' => 'OnlineFederation',
'authMode' => 'Federation',
];
$this->clientSettings = new Settings($this->clientOptions);
$this->client = new Client($this->clientSettings);
$this->metadata = MetadataCollection::instance($this->client);
if ($this->clientSettings->hasOrganizationData()) {
} else {
Log::info('There was an error retrieving organization data for the CRM. Please check connection settings.');
die('There was an error retrieving organization data for the CRM. Please check connection settings.');
}
}
|
@AndyMain Can you modify Client.php and dump Looks like assertion from ADFS is not what we expect but I wonder what it could be considering that your CRM is working just fine. |
Ok I'll get this info for you when I can, most likely next week now. |
@wizardist that would tell us what to expect but not necessarily what's coming back. But agree, it'd be useful. @AndyMain easiest way to get it is to put organization service endpoint into the browser and add ?singlewsdl parameter. |
Here you go hope this helps, noticed you mentioned AD (ActiveDirectory) and this is mentioned prominently at the top... |
@AndyMain yep, that's what I suspected - your instance uses a different authentication method, and WS-SP specifies SpnegoContextToken assertion which we don't support yet. More details later. |
@AndyMain I'm going to close this issue, for further information, please refer to the enhancement ticket created |
Onsite installations (non dynamics.com url's) are not supported but look like they could be with some work.
For example with an onsite installation with the url 'subdomain.domain.ac.uk' the organizationUrl gets built out as;
https://subdomain.api.domain.dynamics.com/XRMServices/2011/Organization.svc
Here as it should be;
https://subdomain.domain.ac.uk/XrmServices/2011/Organization.svc
And the discoveryUrl gets built as;
https://disco.domain.dynamics.com/XRMServices/2011/Discovery.svc
Where it should be;
https://subdomain.domain.ac.uk/XrmServices/2011/Discovery.svc
See alexacrm/php-crm-toolkit/src/Settings.php around line 256 for url parsing.
The text was updated successfully, but these errors were encountered: