Hello everyone I'm trying to retrieve a user data from Active Directory, like Names, departments they belong to etc., and send all that info to a client via REST how can I achieve this?
Also I have a sharepoint application that retrieves part of this info from the AD and is connected via LDAP.
Now what would be the best way to direct all this info to the client via web services I woul prefer REST since is out of the box.
I'm using
Exchange Server 2010 version 14.02.0247.005 and Windows Server 2008 R2
Is this for on-prem Exchange? If so you can use EWS or Powershell. Unfortunately, the only REST services I know of for Exchange are for Office 365.
Here's an overview on MSDN for Exchange 2010 dev.
Related
I'm working on Dynamics since about 1 year, and I'm working on "on premise" environments, and I don't know very much about online solutions.
I should now integrate 2 systems through webservice, and one of them involves Microsoft Dynamics CRM Online 2016.
What I'm trying to accomplish is that the custom systems sends data to the CRM Online through webservice.
I've read I just can't deploy my webservice and my logic as I've always done (separate web application that receives a Json or a XML through web services and works on CRM entities through the SDK).
So, do I need a separate machine to receive the XML and working on the CRM through the SDK?
In some posts I learn a little about Azure, but I don't know if it could be a nice solution. Should I get a virtual machine and then install IIS? Will my web app be visible by the custom system and able to work on the CRM online? Do I need a different service?
Thanks in advance and sorry for the confusion, it's the first time I'm trying to make CRM Online communicate with the outside.
So if I understand correctly your approach is 'custom system <=> your WS <=> CRM Online 2016
I've read I just can't deploy my webservice and my logic as I've always done (separate web application that receives a Json or a XML through web services and works on CRM entities through the SDK).
In CRM Online you don't have access to machine that CRM stands on so no folders, no inetmgr, no deploy.
So, do I need a separate machine to receive the XML and working on the CRM through the SDK?
Yes.
Should I get a virtual machine and then install IIS?
It doesn't have to be new virtual machine. It could be for example machine that custom system stands on ofc. if it can be configured to have access to the internet.
Will my web app be visible by the custom system and able to work on the CRM online?
It is matter of configuration of NAT, firewall etc.
Do I need a different service?
What service do you reffer here?
I'm writing an app which I need to store user details, location and connections in azure db but have no experience with cloud storage. I have created my azure database but not sure how to communicate with the wp7 app. Any thoughts on where to start with the web service,
Thanks, MH
The following may point you in the right direction "Using Windows Phone with Windows Azure
" :-
http://msdn.microsoft.com/en-us/library/windowsazure/hh689721(v=vs.103).aspx
http://windowsteamblog.com/windows_phone/b/wpdev/archive/2011/08/31/building-windows-phone-applications-using-windows-azure.aspx
As to windows phone azure project, do you mean Windows Azure Toolkit for Windows Phone? This toolkit is optional. It may help us in some cases, especially if we want to integrate with ACS. But a web service will be enough if all we need is to bring data to the phone.
Best Regards,
Ming Xu.
To add to Paul’s suggestions, the recommended architecture is: Hosting a service in Windows Azure (such as WCF Data Services). The service will talk to SQL Azure (if you use SQL Azure as the database). Client devices, such as Windows Phone, iPhone, Andriod, a web browser, and so on, will communicate with the service. If you use WCF Data Services, you can expose the data to clients via the OData protocol, which is supported by multiple devices. To get started with WCF Data Services, I would like to suggest you to check http://msdn.microsoft.com/en-us/library/cc668796.aspx. To learn how to consume OData in Windows Phone, please refer to http://blogs.msdn.com/b/phaniraj/archive/2010/03/19/developing-a-windows-phone-7-application-that-consumes-odata.aspx.
Best Regards,
Ming Xu.
We are working on a client app that should search and download directory information from Microsoft OCS server (OCS old as well as Lync).
Does OCS provide web services type api?
From what I understand, the client needs to do sip handshake before it can do directory related queries.
Having dependency on sip stack is not desirable.
So I am wondering if there is a way (like SOAP web service or something like that) to do it.
The client is a C++ client with access to gSoap or curl type library running on Linux platform.
Thanks for your help.
No, there is no web service out of the box that gives you what you need.
I thin your best bet would be to build a UCMA application that would sit on an application server inside your OCS/Lync infrastructure. You could then build a web service to access this.
For OCS 2007, you'd need to use UCMA 1.0. For OCS 2007 R2, UCMA 2.0 and for Lync, UCMA 3.0
We would like to display a list of address. We are trying to design a system where the addresses are only stored in one place, that place being Exchange 2010.
Is there a web service in the Exchange 2010 SDK, that allows us to get the names and address of all users in a group?
Is there a better way to do this, for example getting the data from AD?
I would do this by using the System.DirectoryService.AccountManagement namespace and not through the Exchange Web Services. EWS is more targeted at getting to the information in the Exchange database (email messages, tasks, calendars etc) whereas S.DS.AM is targeted at getting data from Active Directory.
If your domain controllers are running Windows Server 2008 R2 you will have built-in access to web services targetting AD but that's new technology and your company is most likely not using that yet so you'll have to create your own web services wrapping the S.DS.AM-code.
Exchange uses Active Directory to get and update group membership for standard (non-dynamic) Exchange distribution lists so the members of a AD group is the same as the people getting the emails sent to the list. That said, you can use EWS for Expanding Distribution Lists and you might be better off doing this if you're using dynamic distribution groups in Exchange. If you're using dynamic distribution groups in Exchange you need to examine the msExchDynamicDLFilter-value on the dynamic distribution group entry in Active Directory.
So here is the scenario:
I have a MOSS 2007 box and I want my clients to be able to access a SharePoint site via the internet. I am told that I will be using an IPA and AD for authentication. However I have a DB outside of SharePoint that holds various business data and I want to use Web Services to access the data, manipulate it, and send it back to SharePoint via web parts.
The issue is that, from what I understand, I am going to have to authenticate the AD user every time a request to the Web Service happens. Obviously I dont want to do this every time because they have already authenticated to get onto the site, however I do want each call to have some form of security so its not open calls to my db. I do plan on having other applications access this service outside of SharePoint, so I dont want to have to reinstall the service for each application or even again.
Has anyone had to perform this task or something similar or do you have any suggestions on how to do this?
Thank you in advance and happy coding!
Why not just deploy the webservice to Sharepoint using a Sharepoint solution and a Feature.
That way it will be running under the sharepoint app pool and all authentication is done by sp.
Edit:
Seeing that SharePoint should not be in "control" (as stated in the comment), you should create the webservice, and run the application it's under in as using Windows Authentication. IMHO you should create a WCF Service. The, using the information found in this article you make the Service authenticate users against the AD usergroups they are in. see the "Security: Authentication" section of the article.
Then in Visual Studio you create a webpart and add a service reference to the project, pointing to your newly created Service. Have the webpart perform the needed logic (i.e. display data etc.)
Deploy the webpart to SharePoint using a SharePoint solution (.wsp files, created with WSPBuilder). Google for SharePoint + wspbuilder + tutorials. The solution should contain 1 feature to deploy the webpart. WSPBuilder integrates with VS and allows for the creation of WSPBuilde project. add a webpart feature item to the project (it will create the xml (deployment related) and code file for the webpart.