Hi
I'm struggling with the FIM Web service connector in different areas that i need some help with.
For starters i just want to let you know that i've worked a great deal with the connector, and learned how to cope with most of the shortcomings and quirks. My work has mostly been for on-premise tasks, i.e. connecting to other on-premise systems.
Now I am trying to connect to a Web service over the Internet, hence the security setup is significantly different from what I am used to in conjunction with the Web Service Connector.
I this case the web services is https based and also requires a client certificate for authentication.
The client certificate part is actually not a problem as the connector supports authenticating using client certificates natively and it works like a charm.
My problems seems to be around using a https based web service, also that the web service presents itself as supporting both soap and soap12 requests. When I add the web service to the Web Service Configuration Tool, I receive a warning telling that one of my endpoints has a unsupported (custom) binding, that is not a basic http binding. I actually discover two endpoints that seem alike but the failing one is based on soap12. I am not able to remove the failing endpoint within the Web Service Configuration Tool and successive attempts to configure a Management Agent in FIM Sync Manager using this Web Service Project fails as unsupported bindings are used.
According to the hotfix update 1.0.419.911 for the FIM WebService Connector - this update should address certain limitations towards custom bindings, so I tried to implement this update.
But this gave another headache - after updating the Web Service Connector (actually uninstalling the old one, and installing the new one - as there seems to be some versioning mishaps) I am not able to start the Web Service Configuration Console as i am presented with the following error:
---
Error occurred while running the tool
Could not load flie or assemply 'Microsoft.MetaDirectorySericesEx,Version=4.1.2.0...etc...
---
The error is: Strong name validation failed.
I've tried several things to address the issue, i.e.:
- Copying the Microsoft.MetaDirectorySericesEx.dll file from other folder to the UIShell\Web Service Configuration folder as the versions was not alike - resultet in manifest problems.
- Turning off Strong Name Checking for the library in question - the Web Config tools has able to start but crashed when used.
- Upgraded to newest build of FIM Sync (4.1.3559) - still not working.
So - my actual questions are:
- Does the FIM Web Service Connector support accessing web services that are https based in either the old (5.3.407.0) version or the new one (hotfix update 1.0.419.911) ?
- What about soap12?
- Did anyone succeed in implementing the new Web Service Connector update?
- Any hints on solving the problem I encountered with the Web Service Connector ?
Any input highly appreciated.
Best regards
Søren